Elasticsearch 0.90.10

MattW · Jan 12, 2014

Anyone else running this?

I've updated 2 servers to use it, and both are now reporting errors

Code:

[2014-01-12 02:15:49,597][WARN ][index.engine.robin       ] [Blazing Skull] [htl][2] Warm-up failed
java.lang.IllegalMonitorStateException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:503)
        at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822)
        at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99)
        at org.elasticsearch.index.engine.robin.RobinEngine$2.warm(RobinEngine.java:1443)
        at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:4186)
        at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3654)
        at org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:405)
        at org.apache.lucene.index.TrackingConcurrentMergeScheduler.doMerge(TrackingConcurrentMergeScheduler.java:107)
        at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:482)
[2014-01-12 02:17:34,182][WARN ][index.engine.robin       ] [Blazing Skull] [htl][4] failed to prepare/warm
java.lang.IllegalMonitorStateException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:503)
        at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822)
        at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99)
        at org.elasticsearch.index.engine.robin.RobinEngine$RobinSearchFactory.newSearcher(RobinEngine.java:1652)
        at org.apache.lucene.search.SearcherManager.getSearcher(SearcherManager.java:155)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:122)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:58)
        at org.apache.lucene.search.ReferenceManager.doMaybeRefresh(ReferenceManager.java:155)
        at org.apache.lucene.search.ReferenceManager.maybeRefresh(ReferenceManager.java:204)
        at org.elasticsearch.index.engine.robin.RobinEngine.refresh(RobinEngine.java:786)
        at org.elasticsearch.index.shard.service.InternalIndexShard.refresh(InternalIndexShard.java:459)
        at org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher$1.run(InternalIndexShard.java:877)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Code:

root@host [995 02:22:09 /elasticsearch/logs]# curl localhost:9200  
{
  "ok" : true,
  "status" : 200,
  "name" : "Blazing Skull",
  "version" : {
    "number" : "0.90.10",
    "build_hash" : "0a5781f44876e8d1c30b6360628d59cb2a7a2bbb",
    "build_timestamp" : "2014-01-10T10:18:37Z",
    "build_snapshot" : false,
    "lucene_version" : "4.6"
  },
  "tagline" : "You Know, for Search"
}

2nd server

Code:

[2014-01-12 08:11:19,143][WARN ][index.engine.robin       ] [Architect] [z22se][4] failed to prepare/warm
java.lang.IllegalMonitorStateException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:503)
        at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822)
        at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99)
        at org.elasticsearch.index.engine.robin.RobinEngine$RobinSearchFactory.newSearcher(RobinEngine.java:1652)
        at org.apache.lucene.search.SearcherManager.getSearcher(SearcherManager.java:155)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:122)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:58)
        at org.apache.lucene.search.ReferenceManager.doMaybeRefresh(ReferenceManager.java:155)
        at org.apache.lucene.search.ReferenceManager.maybeRefresh(ReferenceManager.java:204)
        at org.elasticsearch.index.engine.robin.RobinEngine.refresh(RobinEngine.java:786)
        at org.elasticsearch.index.shard.service.InternalIndexShard.refresh(InternalIndexShard.java:459)
        at org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher$1.run(InternalIndexShard.java:877)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-01-12 08:14:23,631][WARN ][index.engine.robin       ] [Architect] [z22se][2] failed to prepare/warm
java.lang.IllegalMonitorStateException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:503)
        at org.elasticsearch.search.SearchService$SearchWarmer$2.awaitTermination(SearchService.java:822)
        at org.elasticsearch.indices.warmer.InternalIndicesWarmer.warm(InternalIndicesWarmer.java:99)
        at org.elasticsearch.index.engine.robin.RobinEngine$RobinSearchFactory.newSearcher(RobinEngine.java:1652)
        at org.apache.lucene.search.SearcherManager.getSearcher(SearcherManager.java:155)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:122)
        at org.apache.lucene.search.SearcherManager.refreshIfNeeded(SearcherManager.java:58)
        at org.apache.lucene.search.ReferenceManager.doMaybeRefresh(ReferenceManager.java:155)
        at org.apache.lucene.search.ReferenceManager.maybeRefresh(ReferenceManager.java:204)
        at org.elasticsearch.index.engine.robin.RobinEngine.refresh(RobinEngine.java:786)
        at org.elasticsearch.index.shard.service.InternalIndexShard.refresh(InternalIndexShard.java:459)
        at org.elasticsearch.index.shard.service.InternalIndexShard$EngineRefresher$1.run(InternalIndexShard.java:877)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Code:

[root@astra logs]# curl localhost:9200
{
  "ok" : true,
  "status" : 200,
  "name" : "Architect",
  "version" : {
    "number" : "0.90.10",
    "build_hash" : "0a5781f44876e8d1c30b6360628d59cb2a7a2bbb",
    "build_timestamp" : "2014-01-10T10:18:37Z",
    "build_snapshot" : false,
    "lucene_version" : "4.6"
  },
  "tagline" : "You Know, for Search"
}

MattW · Jan 12, 2014

Downgraded one to 0.90.9 and the errors have gone away

Andy.N · Jan 17, 2014

MattW said:
Downgraded one to 0.90.9 and the errors have gone away

Matt,
Did you figure out the issue?

MattW · Jan 17, 2014

Andy.N said:
Matt,
Did you figure out the issue?

No, it went away with rolling back to 0.90.9

I've updated JRE to 7.0.51 this morning, and built a fresh VPS specifically for ES as a test off the back of this thread : http://xenforo.com/community/threads/high-cpu-load-from-elasticsearch.66489/

mjda · Feb 1, 2014

Did you ever figure out what the issue was here? I'm likely going to be purchase ES within the next few days and would like to know whether or not it would be ok to install the latest version of elasticsearch, or if I need to go ahead and install 0.90.9 too.

MattW · Feb 1, 2014

mjda said:
Did you ever figure out what the issue was here? I'm likely going to be purchase ES within the next few days and would like to know whether or not it would be ok to install the latest version of elasticsearch, or if I need to go ahead and install 0.90.9 too.

No, I've since moved servers, and done a fresh install with 0.90.10 and it's working fine.

Code:

[root@vps logs]# curl localhost:9200
{
  "ok" : true,
  "status" : 200,
  "name" : "Blaquesmith",
  "version" : {
    "number" : "0.90.10",
    "build_hash" : "0a5781f44876e8d1c30b6360628d59cb2a7a2bbb",
    "build_timestamp" : "2014-01-10T10:18:37Z",
    "build_snapshot" : false,
    "lucene_version" : "4.6"
  },
  "tagline" : "You Know, for Search"
}

I think it could have been down to having pre-warmers enabled prior to upgrading, where on the new install, I've not set them this time around.

TheBigK · Feb 1, 2014

Does ES auto-update? I've been noticing strange errors since last 8-10 hours.

MattW · Feb 1, 2014

TheBigK said:
Does ES auto-update? I've been noticing strange errors since last 8-10 hours.

No, it's a manual task.

TheBigK · Feb 1, 2014

MattW said:
No, it's a manual task.

If I move the database; and make it accessible at a new IP; will it affect Elastic search?

Slavik · Feb 1, 2014

TheBigK said:
If I move the database; and make it accessible at a new IP; will it affect Elastic search?

No... ES doesn't access the database directly, XenForo acts as an intemediary between them.

TheBigK · Feb 2, 2014

Slavik said:
No... ES doesn't access the database directly, XenForo acts as an intemediary between them.

Does that mean even if the database is moved to a remote cluster - Elastic Search would still work with 127.0.0.1 and 9200 settings?

MattW · Feb 2, 2014

TheBigK said:
Does that mean even if the database is moved to a remote cluster - Elastic Search would still work with 127.0.0.1 and 9200 settings?

Yes, because it's local to XenForo, not the database. Is ES running on the same server as XenForo (and not the database)?

Slavik · Feb 2, 2014

MattW said:
Yes, because it's local to XenForo, not the database. Is ES running on the same server as XenForo (and not the database)?

Yes

Andy.N · Feb 7, 2014

MattW said:
Downgraded one to 0.90.9 and the errors have gone away

0.90.11 is out. Give it a try, Matt.

Andy.N · Feb 7, 2014

I went ahead and upgraded to 0.90.11 and even doing the same routine like I did in the past, it still shows 0.90.9

rdn · Feb 8, 2014

Is there a guide to upgrade ElasticSearch properly?

Does this steps work fine?

Stop the service
d0wnl0ad the new elasticsearch
Overwrite the files
Re-configure if needed
Restart the service
Reindex.

MattW · Feb 8, 2014

Andy.N said:
0.90.11 is out. Give it a try, Matt.

Mine is working OK on 0.90.10 since I moved servers, so I'm going to stick with that for a while, as it's working fine.

Andy.N · Feb 25, 2014

MattW said:
Mine is working OK on 0.90.10 since I moved servers, so I'm going to stick with that for a while, as it's working fine.

1.0.1 is out today

rdn · Feb 25, 2014

Code:

 curl http://localhost:9200
{
  "status" : 200,
  "name" : "Tombstone",
  "version" : {
    "number" : "1.0.1",
    "build_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b",
    "build_timestamp" : "2014-02-25T15:52:53Z",
    "build_snapshot" : false,
    "lucene_version" : "4.6"
  },
  "tagline" : "You Know, for Search"
}

Elasticsearch 0.90.10

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

XenForo moderator

Well-known member

Well-known member

XenForo moderator

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Similar threads

We value your privacy