vogievetsky 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-507071244 Hi @acdn-mpreston there is a lot to unpack in this issue. 1. You are issue number 8000, congratulations 🎆 2. I am saddened by the issue your console is having rendering icons ] I am guessing you are somehow prevented from loading the icon font? This should be addressed in the newly released Druid 0.15.0 , we upgraded to the latest blueprintjs which no longer uses the icon font. 3. The segments you have highlighted do not really have 0 rows num_rows is only reported for available segments. This is confusing UI and will be fixed in the next iteration of the web console (in 0.16.0). It will then say `(unknown)`. 4. The segments you have highlighted are actually the segments you want! Look at the version it is higher. Maybe they are the result of the compaction and they have not been loaded yet? 5. More info is needed to understand what is going on: by `I started to notice long periods of time when our datasources would not be 100% available` what do you mean by 'long' minutes? hours? days? Also when you say `Eventually these rows get cleaned up` can you be specific on 'Eventually' is it minutes? hours?
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
