Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store shard size on disk statistic #6664

Merged
merged 2 commits into from
May 18, 2016
Merged

Store shard size on disk statistic #6664

merged 2 commits into from
May 18, 2016

Conversation

e-dard
Copy link
Contributor

@e-dard e-dard commented May 18, 2016

Required for all non-trivial PRs
  • Rebased/mergable
  • Tests pass
  • CHANGELOG.md updated

This PR adds a monitoring goroutine to each shard, which will periodically emit a statistic with the current on-disk size of the shard.

@jwilder

/cc @sparrc

@e-dard e-dard force-pushed the jw-shard-size branch 3 times, most recently from 5638e3d to c2535c5 Compare May 18, 2016 17:33
@jwilder
Copy link
Contributor

jwilder commented May 18, 2016

👍

@jwilder jwilder added this to the 1.0.0 milestone May 18, 2016
@e-dard e-dard merged commit 09dc48b into master May 18, 2016
@e-dard e-dard deleted the jw-shard-size branch May 18, 2016 21:39
@@ -173,6 +181,8 @@ func (s *Shard) Open() error {
}
s.logger.Printf("%s database index loaded in %s", s.path, time.Now().Sub(start))

go s.monitorSize()
Copy link
Member

@pauldix pauldix May 20, 2016

Choose a reason for hiding this comment

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

do we have a separate goroutine for monitoring each individual stat? Seems like we should come up with a design where on goroutine gathers all stats directly?

Copy link
Contributor

Choose a reason for hiding this comment

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

Just this stat right now. I agree that we need to have a polling model. Unfortunately, we need to rework the monitoring framework quite a bit to allow it it pull stats like this that are too complicated to track in real time.

@timhallinflux timhallinflux modified the milestones: 1.0.0, 1.0.0 beta Dec 19, 2016
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.

4 participants