I'll keep this short and I hope its just a misunderstanding of java on my
part.
All my Elasticsearch nodes are reporting a JVM uptime between 1 and 25
hours. The strange part is all the JAVA process have a start date of 9+
days. How can the JVM uptime be less than the JAVA process time? I see
nothing in the Elasticsearch logs with any indication of the issue. Thanks
for your help.
I'll keep this short and I hope its just a misunderstanding of java on my
part.
All my Elasticsearch nodes are reporting a JVM uptime between 1 and 25
hours. The strange part is all the JAVA process have a start date of 9+
days. How can the JVM uptime be less than the JAVA process time? I see
nothing in the Elasticsearch logs with any indication of the issue. Thanks
for your help.
I was thinking the same thing, except every ~25 hours the jvm uptime resets
back to zero, but the java pid and start time remain unchanged.
On Tuesday, March 25, 2014 6:03:15 PM UTC-7, Nelson Jeppesen wrote:
I'll keep this short and I hope its just a misunderstanding of java on my
part.
All my Elasticsearch nodes are reporting a JVM uptime between 1 and 25
hours. The strange part is all the JAVA process have a start date of 9+
days. How can the JVM uptime be less than the JAVA process time? I see
nothing in the Elasticsearch logs with any indication of the issue. Thanks
for your help.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.