You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/07/02 14:18:31 UTC
[GitHub] [incubator-druid] acdn-mpreston commented on issue #8000:
Datasource availability mis-represented due to 0 row segments not cleaned
up after compaction
acdn-mpreston commented on issue #8000: Datasource availability mis-represented due to 0 row segments not cleaned up after compaction
URL: https://github.com/apache/incubator-druid/issues/8000#issuecomment-507697896
Hey @vogievetsky, thanks for the quick attention!
1. Thanks!!!
2. Awesome.
3. That makes more sense, thank you.
4. You are correct, I made an assumption based on the "Num rows" being populated and the "Is available" flag being set to true....interesting that there are 3 different versions of the segments all published at the same time.
5. For the datasource availability, majority of the time it has not been 100%. Here is a graph showing the availability returned over a couple day period where we call the loadstatus API every minute:
Sometimes it will be 100% available, but not regularly. As you can see, it is almost always VERY close to 100% but not 100%. If I query the data, it is always there....no segments are missing it just seems that there is segment tracking that is confused.
In terms of resolution, it takes many minutes or even maybe an hour, to resolve the mis-represented segments.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org