Skip to content

Add ability to skip loadSpec,dimensions, metrics from DataSegment Announcements#2784

Merged
b-slim merged 1 commit intoapache:masterfrom
metamx:lite-segment-announcements
Apr 7, 2016
Merged

Add ability to skip loadSpec,dimensions, metrics from DataSegment Announcements#2784
b-slim merged 1 commit intoapache:masterfrom
metamx:lite-segment-announcements

Conversation

@nishantmonu51
Copy link
Copy Markdown
Member

  • Add Ability to skip list of dimensions, metrics and loadSpec from segment announcements.
  • Default behavior is unchanged.

This can be useful in order to reduce the heap pressure on the coordinator and broker when the number of DataSegments to be tracked are huge.
Note: Broker/coordinator end points that expose list of dimensions & metrics will report empty set of dimensions and metrics if skipDimensions and skipMetrics are set to true. However this info can still be queried using SegmentMetadataQuery.

@b-slim
Copy link
Copy Markdown
Contributor

b-slim commented Apr 4, 2016

👍

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these wil need to be documented

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added docs

@fjy
Copy link
Copy Markdown
Contributor

fjy commented Apr 4, 2016

👍 after docs are added

@fjy fjy added this to the 0.9.1 milestone Apr 4, 2016
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need separate configs for dimensions and metrics? Is there any use in having one but not the other?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added separate config in case someone has any tools built on top which needs metrics list and not dimensions list or vice versa.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does it actually make sense to have one but not the other?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

created #2821 for follow up.

@fjy
Copy link
Copy Markdown
Contributor

fjy commented Apr 5, 2016

@nishantmonu51 conflicts

separate config for each skipping dimensions, metrics and loadSpec

Add test

fix test comment

Add docs
@nishantmonu51 nishantmonu51 force-pushed the lite-segment-announcements branch from 16c3fe1 to edd74f2 Compare April 7, 2016 12:54
@nishantmonu51
Copy link
Copy Markdown
Member Author

@fjy: resolved conflicts and added docs.

@b-slim b-slim merged commit d5787dd into apache:master Apr 7, 2016
@xvrl
Copy link
Copy Markdown
Member

xvrl commented Apr 8, 2016

@b-slim I still had some comments outstanding on this one, it would have been nice to wait for my +1

@b-slim
Copy link
Copy Markdown
Contributor

b-slim commented Apr 12, 2016

@xvrl sorry I haven't seen that.

nishantmonu51 added a commit to metamx/druid that referenced this pull request Apr 12, 2016
@nishantmonu51 nishantmonu51 deleted the lite-segment-announcements branch April 12, 2016 17:48
@licl2014
Copy link
Copy Markdown
Contributor

licl2014 commented Oct 7, 2018

image
@nishantmonu51 @fjy Thanks for this issue, I find a lot of Full gc information in my coordinator gc log, then i dump the memory of coordinator and find many RegularImmutableList about dimensions and metrics , the vesion of druid we used is 0.9.2.

@licl2014
Copy link
Copy Markdown
Contributor

licl2014 commented Oct 8, 2018

After setting druid.announcer.skipDimensionsAndMetrics to true, metric information and dimension information in coordinator page will disappeared ,it seems not friendly for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants