You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Allan Yang (JIRA)" <ji...@apache.org> on 2018/10/24 02:07:00 UTC
[jira] [Comment Edited] (HBASE-21372) Set
hbase.assignment.maximum.attempts to Long.MAX
[ https://issues.apache.org/jira/browse/HBASE-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661606#comment-16661606 ]
Allan Yang edited comment on HBASE-21372 at 10/24/18 2:06 AM:
--------------------------------------------------------------
+1 for it.
TransitRegionStateProcedure is introduced in branch-2+ by [~Apache9], can [~Apache9] conform that in branch-2+, we have already retry forever for assignment?
was (Author: allan163):
+1 for it, TransitRegionStateProcedure is introduced in branch-2+ by [~Apache9], can [~Apache9] conform that in branch-2+, we have already retry forever for assignment?
> Set hbase.assignment.maximum.attempts to Long.MAX
> -------------------------------------------------
>
> Key: HBASE-21372
> URL: https://issues.apache.org/jira/browse/HBASE-21372
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Major
> Attachments: HBASE-21372.branch-2.1.001.patch, HBASE-21372.branch-2.1.001.patch
>
>
> From parent issue, [~allan163] suggests that we not give up on assign unless there a change -- an SCP triggers failure -- or at the extreme, an operator intervenes. This jibes w/ how we're thinking about assign (or to put it another way, we have no handling for the case where we exhaust retries).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)