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 2018/08/15 00:36:34 UTC

[GitHub] gianm opened a new issue #6176: CuratorInventoryManager may not report inventory as initialized

gianm opened a new issue #6176: CuratorInventoryManager may not report inventory as initialized
URL: https://github.com/apache/incubator-druid/issues/6176
 
 
   The reason is unclear, but we've seen brokers running 0.12.1 fail to report "Inventory Initialized" events even after running for long periods of time. Nevertheless, the broker seems to be able to do native queries normally, and seems to be properly aware of all historicals. Restarting the broker generally clears this up. It seems to be somewhat random whether or not this will occur on any given broker startup.
   
   This has one knock-on effect: DruidSchema (the SQL layer's metadata cache) doesn't activate until after inventory is initialized, and so this blocks the SQL layer from working. It just reports that there are no tables.
   
   Checking /druid/broker/v1/loadstatus returns false when the broker is in this state.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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