1.0.0RC1 breaking changes : GC stats

Elastic Stack Elasticsearch
1

Well, not sure if it qualifies as a breaking change, unless you cowboy code
javascript like I do :wink:

The node stats api (/_nodes/{this.nodeId}/stats?all=1) is returning a
different format for JVM GC now, splitting old and young generations (which
is really helpful)

I didn't notice this change in Beta1, so I thought I'd point it out and
maybe someone can/might update the doc.

        "gc": {
           "collectors": {
              "young": {
                 "collection_count": 3,
                 "collection_time_in_millis": 136
              },
              "old": {
                 "collection_count": 0,
                 "collection_time_in_millis": 0
              }
           }

I also didn't notice previously the jvm returning pool information (another
helpful addition!)

           "pools": {
              "young": {
                 "used_in_bytes": 30180776,
                 "max_in_bytes": 279183360,
                 "peak_used_in_bytes": 71630848,
                 "peak_max_in_bytes": 279183360
              },
              "survivor": {
                 "used_in_bytes": 8912888,
                 "max_in_bytes": 34865152,
                 "peak_used_in_bytes": 8912896,
                 "peak_max_in_bytes": 34865152
              },
              "old": {
                 "used_in_bytes": 21765456,
                 "max_in_bytes": 724828160,
                 "peak_used_in_bytes": 21765456,
                 "peak_max_in_bytes": 724828160
              }
           }

--
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/da092537-d6b7-4870-81fa-ed599fe610ea%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

2

It appears these changes may not be new, and simply a symptom of my moving
to G1GC... disregard my mad ramblings.

On Monday, January 20, 2014 11:41:54 AM UTC-5, Roy Russo wrote:

Well, not sure if it qualifies as a breaking change, unless you cowboy
code javascript like I do :wink:

The node stats api (/_nodes/{this.nodeId}/stats?all=1) is returning a
different format for JVM GC now, splitting old and young generations (which
is really helpful)

I didn't notice this change in Beta1, so I thought I'd point it out and
maybe someone can/might update the doc.

        "gc": {
           "collectors": {
              "young": {
                 "collection_count": 3,
                 "collection_time_in_millis": 136
              },
              "old": {
                 "collection_count": 0,
                 "collection_time_in_millis": 0
              }
           }

I also didn't notice previously the jvm returning pool information
(another helpful addition!)

           "pools": {
              "young": {
                 "used_in_bytes": 30180776,
                 "max_in_bytes": 279183360,
                 "peak_used_in_bytes": 71630848,
                 "peak_max_in_bytes": 279183360
              },
              "survivor": {
                 "used_in_bytes": 8912888,
                 "max_in_bytes": 34865152,
                 "peak_used_in_bytes": 8912896,
                 "peak_max_in_bytes": 34865152
              },
              "old": {
                 "used_in_bytes": 21765456,
                 "max_in_bytes": 724828160,
                 "peak_used_in_bytes": 21765456,
                 "peak_max_in_bytes": 724828160
              }
           }

--
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/fecc0335-05b2-4c27-963f-a85dc002a253%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

Hi Roy,
I think you are referring to this recent
change: Create standard gc and memory_pool names for Jvm stats 路 Issue #4661 路 elastic/elasticsearch 路 GitHub .

The same information was already there, but depending on the type of
garbage collector had different names. We decided to standardize under old
and young and survivor, using the same names in all cases.

On Monday, January 20, 2014 5:44:59 PM UTC+1, Roy Russo wrote:

It appears these changes may not be new, and simply a symptom of my moving
to G1GC... disregard my mad ramblings.

On Monday, January 20, 2014 11:41:54 AM UTC-5, Roy Russo wrote:

Well, not sure if it qualifies as a breaking change, unless you cowboy
code javascript like I do :wink:

The node stats api (/_nodes/{this.nodeId}/stats?all=1) is returning a
different format for JVM GC now, splitting old and young generations (which
is really helpful)

I didn't notice this change in Beta1, so I thought I'd point it out and
maybe someone can/might update the doc.

        "gc": {
           "collectors": {
              "young": {
                 "collection_count": 3,
                 "collection_time_in_millis": 136
              },
              "old": {
                 "collection_count": 0,
                 "collection_time_in_millis": 0
              }
           }

I also didn't notice previously the jvm returning pool information
(another helpful addition!)

           "pools": {
              "young": {
                 "used_in_bytes": 30180776,
                 "max_in_bytes": 279183360,
                 "peak_used_in_bytes": 71630848,
                 "peak_max_in_bytes": 279183360
              },
              "survivor": {
                 "used_in_bytes": 8912888,
                 "max_in_bytes": 34865152,
                 "peak_used_in_bytes": 8912896,
                 "peak_max_in_bytes": 34865152
              },
              "old": {
                 "used_in_bytes": 21765456,
                 "max_in_bytes": 724828160,
                 "peak_used_in_bytes": 21765456,
                 "peak_max_in_bytes": 724828160
              }
           }

--
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/535ecdd8-52e0-40ac-9ef6-23a83fa1679c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

4

Yes. Thanks, Luca. The ticket does call it a breaking change, but I must've
somehow missed the information in the old format.

On Mon, Jan 20, 2014 at 12:27 PM, Luca Cavanna cavannaluca@gmail.comwrote:

Hi Roy,
I think you are referring to this recent change:
Create standard gc and memory_pool names for Jvm stats 路 Issue #4661 路 elastic/elasticsearch 路 GitHub .

The same information was already there, but depending on the type of
garbage collector had different names. We decided to standardize under old
and young and survivor, using the same names in all cases.

On Monday, January 20, 2014 5:44:59 PM UTC+1, Roy Russo wrote:

It appears these changes may not be new, and simply a symptom of my
moving to G1GC... disregard my mad ramblings.

On Monday, January 20, 2014 11:41:54 AM UTC-5, Roy Russo wrote:

Well, not sure if it qualifies as a breaking change, unless you cowboy
code javascript like I do :wink:

The node stats api (/_nodes/{this.nodeId}/stats?all=1) is returning a
different format for JVM GC now, splitting old and young generations (which
is really helpful)

I didn't notice this change in Beta1, so I thought I'd point it out and
maybe someone can/might update the doc.

        "gc": {
           "collectors": {
              "young": {
                 "collection_count": 3,
                 "collection_time_in_millis": 136
              },
              "old": {
                 "collection_count": 0,
                 "collection_time_in_millis": 0
              }
           }

I also didn't notice previously the jvm returning pool information
(another helpful addition!)

           "pools": {
              "young": {
                 "used_in_bytes": 30180776,
                 "max_in_bytes": 279183360,
                 "peak_used_in_bytes": 71630848,
                 "peak_max_in_bytes": 279183360
              },
              "survivor": {
                 "used_in_bytes": 8912888,
                 "max_in_bytes": 34865152,
                 "peak_used_in_bytes": 8912896,
                 "peak_max_in_bytes": 34865152
              },
              "old": {
                 "used_in_bytes": 21765456,
                 "max_in_bytes": 724828160,
                 "peak_used_in_bytes": 21765456,
                 "peak_max_in_bytes": 724828160
              }
           }

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/6paUZ1i5AfI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/535ecdd8-52e0-40ac-9ef6-23a83fa1679c%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
Regards,
Roy Russo
404.453.9596
http://www.linkedin.com/in/royrusso

--
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/CANTOpgsR30XQaFPPM5QtNs47gD1rZ5--nf-aHoOCWUWaCKjZjA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.