[jira] [Updated] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
[ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18491: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thats sweet that that is all it took to fix the failing test. I like this. This is the way it should be. Thanks [~uagashe] > [AMv2] Fail UnassignProcedure if source Region Server is not online. > > > Key: HBASE-18491 > URL: https://issues.apache.org/jira/browse/HBASE-18491 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Critical > Fix For: 2.0.0 > > Attachments: hbase-18491.master.001.patch > > > Currently UnassignProcedure returns success when server carrying a region is > NOT online. Assumption here is that ServerCrashProcedure will handle > splitting logs etc for these regions. When UnassignProcedure completes, > MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some > times assign regions without pre-requisite steps (done either by > UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure > and parent MoveRegionProcedure if source server is not online. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
[ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18491: - Priority: Critical (was: Major) > [AMv2] Fail UnassignProcedure if source Region Server is not online. > > > Key: HBASE-18491 > URL: https://issues.apache.org/jira/browse/HBASE-18491 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Critical > Fix For: 2.0.0 > > Attachments: hbase-18491.master.001.patch > > > Currently UnassignProcedure returns success when server carrying a region is > NOT online. Assumption here is that ServerCrashProcedure will handle > splitting logs etc for these regions. When UnassignProcedure completes, > MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some > times assign regions without pre-requisite steps (done either by > UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure > and parent MoveRegionProcedure if source server is not online. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
[ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18491: - Status: Patch Available (was: In Progress) > [AMv2] Fail UnassignProcedure if source Region Server is not online. > > > Key: HBASE-18491 > URL: https://issues.apache.org/jira/browse/HBASE-18491 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18491.master.001.patch > > > Currently UnassignProcedure returns success when server carrying a region is > NOT online. Assumption here is that ServerCrashProcedure will handle > splitting logs etc for these regions. When UnassignProcedure completes, > MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some > times assign regions without pre-requisite steps (done either by > UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure > and parent MoveRegionProcedure if source server is not online. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
[ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18491: - Attachment: hbase-18491.master.001.patch Lets see if unit tests pass. > [AMv2] Fail UnassignProcedure if source Region Server is not online. > > > Key: HBASE-18491 > URL: https://issues.apache.org/jira/browse/HBASE-18491 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18491.master.001.patch > > > Currently UnassignProcedure returns success when server carrying a region is > NOT online. Assumption here is that ServerCrashProcedure will handle > splitting logs etc for these regions. When UnassignProcedure completes, > MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some > times assign regions without pre-requisite steps (done either by > UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure > and parent MoveRegionProcedure if source server is not online. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
[ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18491: - Component/s: amv2 > [AMv2] Fail UnassignProcedure if source Region Server is not online. > > > Key: HBASE-18491 > URL: https://issues.apache.org/jira/browse/HBASE-18491 > Project: HBase > Issue Type: Bug > Components: amv2 >Affects Versions: 2.0.0 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > > Currently UnassignProcedure returns success when server carrying a region is > NOT online. Assumption here is that ServerCrashProcedure will handle > splitting logs etc for these regions. When UnassignProcedure completes, > MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some > times assign regions without pre-requisite steps (done either by > UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure > and parent MoveRegionProcedure if source server is not online. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
