Replica indexing failure

Hi,
Our ES installation has been running stable so far, except since yesterday
we are getting these failures sporadically. You can see a snippet of error
log here: https://gist.github.com/3150299
Could it be JVM issue? Following is the output of java -version:
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.13) (6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)

Any suggestions?

Cheers
Nitish

On Fri, 2012-07-20 at 04:45 -0700, Nitish Sharma wrote:

Hi,
Our ES installation has been running stable so far, except since
yesterday we are getting these failures sporadically. You can see a
snippet of error log here: Replica indexing failure · GitHub

Could it be JVM issue? Following is the output of java -version:
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.13)
(6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)

No. You're passing it bad data.

clint

Hi Clinton,
That could be one of the reasons. But, for us, usually these kind of errors
are accompanied by:
[monitor.jvm ] [node1] [gc][ParNew][31993][57678] duration
[1.5s], collections [1]/[1.7s], total [1.5s]/[29.6m], memory
[3.8gb]->[3.7gb]/[15.9gb], all_pools {[Code Cache]
[10.2mb]->[10.2mb]/[48mb]}{[Par Eden Space] [18.6mb]->[1mb]/[133.1mb]}{[Par
Survivor Space] [3.5mb]->[3.5mb]/[16.6mb]}{[CMS Old Gen]
[3.7gb]->[3.7gb]/[15.8gb]}{[CMS Perm Gen] [47.9mb]->[47.9mb]/[166mb]}

Any thoughts?

Cheers
Nitish
On Friday, July 20, 2012 2:18:17 PM UTC+2, Clinton Gormley wrote:

On Fri, 2012-07-20 at 04:45 -0700, Nitish Sharma wrote:

Hi,
Our ES installation has been running stable so far, except since
yesterday we are getting these failures sporadically. You can see a
snippet of error log here: Replica indexing failure · GitHub

Could it be JVM issue? Following is the output of java -version:
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.13)
(6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)

No. You're passing it bad data.

clint

Hi Nitish

That could be one of the reasons. But, for us, usually these kind of
errors are accompanied by:
[monitor.jvm ] [node1] [gc][ParNew][31993][57678]
duration [1.5s], collections [1]/[1.7s], total [1.5s]/[29.6m], memory
[3.8gb]->[3.7gb]/[15.9gb], all_pools {[Code Cache]
[10.2mb]->[10.2mb]/[48mb]}{[Par Eden Space]
[18.6mb]->[1mb]/[133.1mb]}{[Par Survivor Space]
[3.5mb]->[3.5mb]/[16.6mb]}{[CMS Old Gen]
[3.7gb]->[3.7gb]/[15.8gb]}{[CMS Perm Gen] [47.9mb]->[47.9mb]/[166mb]}

That's not an error. That's just logging garbage collection

clint