You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2020/06/23 18:03:21 UTC

[GitHub] [hbase] huaxiangsun commented on pull request #1933: HBASE-24588 : Submit task for NormalizationPlan

huaxiangsun commented on pull request #1933:
URL: https://github.com/apache/hbase/pull/1933#issuecomment-648325944


   > @ndimiduk @huaxiangsun
   > 
   > I agree with logging "N plans submitted". That looks perfectly fine. Added commit for the same.
   > 
   > So, now remains the only concern: `how we deal with concurrent normalizer runs`. Maybe we should strictly follow 5 min gap at least? NormalizerChore also has default 5 min interval, but client can trigger normalizer run through Admin interface.
   > If not 5 min, maybe some smaller cool off interval (2 min)? What do you think? Any better thoughts to prevent concurrent runs?
   > 
   > Basically, I am talking about last execution timestamp check in addition to ReentrantLock which we already have.
   
   Not sure if we need to do this kind of check. For most of the clusters, I think 5 mins is too short.
   
   


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