# 0.19.3 Released

**URL:** <https://discuss.elastic.co/t/0-19-3-released/7513>\
**Category:** Elasticsearch\
**Created:** [April 30, 2012, 11:03am UTC](https://discuss.elastic.co/t/0-19-3-released/7513 "2012-04-30T11:03:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [April 30, 2012, 11:03am UTC](https://discuss.elastic.co/t/0-19-3-released/7513/1 "2012-04-30T11:03:20Z")

</div>

Heya,

0.19.3 was just released, more details here:  
[http://www.elasticsearch.org/blog/2012/04/30/0.19.3-released.html](http://www.elasticsearch.org/blog/2012/04/30/0.19.3-released.html).

cheers,  
-shay.banon

---

<div class="post-metadata">

**Author:** ![jagdeep](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jagdeep](https://discuss.elastic.co/u/jagdeep)\
**Post date:** [April 30, 2012, 5:49pm UTC](https://discuss.elastic.co/t/0-19-3-released/7513/2 "2012-04-30T17:49:43Z")

</div>

Thnaks Shay for the new release.

I have recently upgraded my production environment to 0.19.2 but I am  
facing a issue in server recovery after java heap space error. This is  
particularly happening when I have multiple nodes(2 nodes on one  
server and 4 nodes on other server). Its able to successfully recover  
if only one node is up. The complete elasticsearch setup becomes  
unresponsive after heap error.  
Will upgrading to 0.19.3 help me addressing this issue.

Thanks and Regards  
Jagdeep

On Apr 30, 4:03 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> Heya,
> 
> 0.19.3 was just released, more details here:[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/2012/04/30/0.19.3-released.html).
> 
> cheers,  
> -shay.banon

---

<div class="post-metadata">

**Author:** ![jagdeep](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jagdeep](https://discuss.elastic.co/u/jagdeep)\
**Post date:** [April 30, 2012, 6:03pm UTC](https://discuss.elastic.co/t/0-19-3-released/7513/3 "2012-04-30T18:03:59Z")

</div>

I have gone through below link

> **[What Is Elasticsearch: Getting Started Tutorial for Beginners - Sematext](https://sematext.com/guides/elasticsearch/)**
>
> Get started with Elasticsearch! Detailed tutorial to learn the basic concepts: what is Elasticsearch, how it works, and what it is used for.

My reason to run multiple nodes on 1 server is a constraint of windows  
32 bit. I have 32 GB ram but not able to allocate more than 1.5GB to  
ES thats why running multiple instances.

Thanks and Regards  
Jagdeep

On Apr 30, 10:49 pm, jagdeep singh [reach.jagd...@gmail.com](mailto:reach.jagd...@gmail.com) wrote:

> Thnaks Shay for the new release.
> 
> I have recently upgraded my production environment to 0.19.2 but I am  
> facing a issue in server recovery after java heap space error. This is  
> particularly happening when I have multiple nodes(2 nodes on one  
> server and 4 nodes on other server). Its able to successfully recover  
> if only one node is up. The complete elasticsearch setup becomes  
> unresponsive after heap error.  
> Will upgrading to 0.19.3 help me addressing this issue.
> 
> Thanks and Regards  
> Jagdeep
> 
> On Apr 30, 4:03 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 
> > Heya,
> 
> > 0.19.3 was just released, more details here:[Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/2012/04/30/0.19.3-released.html).
> 
> > cheers,  
> > -shay.banon

---

<div class="post-metadata">

**Author:** ![Alexander\_Reelsen](https://avatars.discourse-cdn.com/v4/letter/a/85e7bf/32.png) [@Alexander\_Reelsen](https://discuss.elastic.co/u/Alexander_Reelsen)\
**Post date:** [April 30, 2012, 9:40pm UTC](https://discuss.elastic.co/t/0-19-3-released/7513/4 "2012-04-30T21:40:14Z")

</div>

Hi there,

just tried to compile my suggester plugin. After replacing some  
deprecated lucene API calls, I noticed my tests cannot start a node  
anymore due to these Guice errors:

1. No implementation for org.elasticsearch.common.settings.Settings  
annotated with @org.elasticsearch.index.settings.IndexSettings() was  
bound.  
while locating org.elasticsearch.common.settings.Settings annotated  
with @org.elasticsearch.index.settings.IndexSettings()  
for parameter 1 at  
org.elasticsearch.index.suggest.ShardSuggestService.(Unknown  
Source)  
at  
org.elasticsearch.module.suggest.SuggestModule.configure(SuggestModule.java:

2. 
3. Could not find a suitable constructor in  
org.elasticsearch.index.shard.ShardId. Classes must have either one  
(and only one) constructor annotated with @Inject or a zero-argument  
constructor that is not private.  
at org.elasticsearch.index.shard.ShardId.class(Unknown Source)  
while locating org.elasticsearch.index.shard.ShardId  
for parameter 0 at  
org.elasticsearch.index.suggest.ShardSuggestService.(Unknown  
Source)  
at  
org.elasticsearch.module.suggest.SuggestModule.configure(SuggestModule.java:

4. 

My ShardSuggestService looks like this:

public class ShardSuggestService extends AbstractIndexShardComponent {  
@Inject  
public ShardSuggestService(ShardId shardId, @IndexSettings  
Settings indexSettings) {  
super(shardId, indexSettings);  
}

Anything wrong with my plugin. Did I miss some API changes or is there  
something more stupid on my side? 🙂

Thanks for helping!

--Alexander

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [May 1, 2012, 3:01pm UTC](https://discuss.elastic.co/t/0-19-3-released/7513/5 "2012-05-01T15:01:54Z")

</div>

No, nothing really changed in that regard. Did you just upgrade your  
suggester plugin to 0.19.4 and you got the error?

On Tue, May 1, 2012 at 12:40 AM, Alexander Reelsen \<  
[alexander.reelsen@googlemail.com](mailto:alexander.reelsen@googlemail.com)\> wrote:

> Hi there,
> 
> just tried to compile my suggester plugin. After replacing some  
> deprecated lucene API calls, I noticed my tests cannot start a node  
> anymore due to these Guice errors:
> 
> 1. No implementation for org.elasticsearch.common.settings.Settings  
> annotated with @org.elasticsearch.index.settings.IndexSettings() was  
> bound.  
> while locating org.elasticsearch.common.settings.Settings annotated  
> with @org.elasticsearch.index.settings.IndexSettings()  
> for parameter 1 at  
> org.elasticsearch.index.suggest.ShardSuggestService.(Unknown  
> Source)  
> at
> 
> org.elasticsearch.module.suggest.SuggestModule.configure(SuggestModule.java:  
> 16)
> 
> 1. Could not find a suitable constructor in  
> org.elasticsearch.index.shard.ShardId. Classes must have either one  
> (and only one) constructor annotated with @Inject or a zero-argument  
> constructor that is not private.  
> at org.elasticsearch.index.shard.ShardId.class(Unknown Source)  
> while locating org.elasticsearch.index.shard.ShardId  
> for parameter 0 at  
> org.elasticsearch.index.suggest.ShardSuggestService.(Unknown  
> Source)  
> at
> 
> org.elasticsearch.module.suggest.SuggestModule.configure(SuggestModule.java:  
> 16)
> 
> My ShardSuggestService looks like this:
> 
> public class ShardSuggestService extends AbstractIndexShardComponent {  
> @Inject  
> public ShardSuggestService(ShardId shardId, @IndexSettings  
> Settings indexSettings) {  
> super(shardId, indexSettings);  
> }
> 
> Anything wrong with my plugin. Did I miss some API changes or is there  
> something more stupid on my side? 🙂
> 
> Thanks for helping!
> 
> --Alexander

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:30am UTC](https://discuss.elastic.co/t/0-19-3-released/7513/6 "2017-07-06T03:30:25Z")

</div>

Closed on July 6, 2017, 3:30am UTC


