[GitHub] [incubator-druid] glasser commented on issue #7180: [PROPOSAL] Cluster names to prevent multiple Druid clusters from interfering with each other

[GitBox <gi...@apache.org>]

glasser commented on issue #7180: [PROPOSAL] Cluster names to prevent multiple Druid clusters from interfering with each other
URL: https://github.com/apache/incubator-druid/issues/7180#issuecomment-469077048
 
 
   @jihoonson I think it would be OK to treat that as "don't use the segment cache" (treat as empty or refuse to start up) — if one file in the segment cache is corrupted, why would any other file be more trustworthy?
   
   @drcrallen Yes, in retrospect it is blindingly obvious how many things we could have done to avoid this issue. But we failed to do so, and the failure mode was incredibly scary.  Our cluster nearly instantly dropped the majority of its data. Even once it was "fixed" it took hours for historicals to reload. And had we not turned off kill tasks that morning we could have permanently lost most of our data.  I do think doing something to avoid the severity of the issue would be a good idea. Plus I want the cluster name in the web console :)

----------------------------------------------------------------
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