JVM uptime less than JAVA process uptime?

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.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f906f9f4-79f9-496b-aee4-220c6029d5b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

At a guess, it might mean the actual time it spent processing, as opposed
to service runtime.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 26 March 2014 12:03, Nelson Jeppesen nelson.jeppesen@gmail.com 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.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f906f9f4-79f9-496b-aee4-220c6029d5b3%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/f906f9f4-79f9-496b-aee4-220c6029d5b3%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Y%2BRzPpn0zDc6UBxCJ8C%2BdvE2XPD8Hre7QYABbnWmG4LA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d1be65c7-c05b-485a-815d-81ec7b231591%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.