You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/04/11 17:02:39 UTC

[GitHub] [nifi] lfrancke commented on issue #3425: NIFI-6197 HBase: Fix deprecations, default for client retries & validations

lfrancke commented on issue #3425: NIFI-6197 HBase: Fix deprecations, default for client retries & validations
URL: https://github.com/apache/nifi/pull/3425#issuecomment-482202372
 
 
   I disagree but I do understand that we don't want a bad user experience :)
   
   I believe the most common scenario is during normal operation. Because having a region moved, split, merged or writes blocked (due to all kinds of reasons) or a server crash is totally normal in HBase. And if you have a long running flow this'll happen multiple times a day on a busy cluster.
   
   Enabling the service will ideally only ever happen once (or very few times).
   
   I don't have time to look now and don't know the API very well but can we use a low retry number for enabling to see if it works and if it does then reconnect with the "proper" number? Shouldn't add much latency.
   
   5 is too low for normal operations. HBase uses an incremental backoff for some of those retries. I believe the current (HBase 2.x) default of 15 to be fine.

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