You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ddanielr (via GitHub)" <gi...@apache.org> on 2023/03/07 02:33:32 UTC

[GitHub] [accumulo] ddanielr commented on issue #3211: OnDemand Tables: Determine how OnDemand tablets are brought online

ddanielr commented on issue #3211:
URL: https://github.com/apache/accumulo/issues/3211#issuecomment-1457409313

   I started looking through [#37](https://github.com/dlmarion/accumulo/pull/37) and I had a functional/process question. 
   
   If all tablets are "offline" by default, then an accumulo cluster will exist with a higher number of tablets then the amount of tserver resources could fully host.  
   
   With that in mind, I have a couple questions
   1. Is there a mechanism to alert on approaching resource limits or evaluate the cluster's current size/use before marking a tablet as onDemand? 
   2. Given the possibility of a limited resource footprint,  what mechanism is going to be used for scheduling the tablet hosting?
   3. What determines hosting priority of onDemand tables? should this exist? should it be a per-client setting or perhaps per table? 
   4. Are "resources unavailable for hosting" an error condition that can be handled for onDemand tables? 
   5. Is there a possibility of scheduling deadlock situations? 


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

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org