subject:"\[jira\] \[Commented\] \(HBASE\-21271\) \[amv2\] Don't throw UnsupportedOperationException when rollback called on Assign\/Unassign; spiral of death"

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-13 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648901#comment-16648901
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.0
[build #944 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/944/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/944//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/944//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/944//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch, 
> HBASE-21271.branch-2.1.002.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-13 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648884#comment-16648884
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.1
[build #459 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/459/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/459//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/459//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/459//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch, 
> HBASE-21271.branch-2.1.002.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-12 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648737#comment-16648737
 ] 

Hadoop QA commented on HBASE-21271:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}  
0m  0s{color} | {color:orange} The patch doesn't appear to include any new or 
modified tests. Please justify why no new tests are needed for this patch. Also 
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-2.1 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
34s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
50s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
15s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
40s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
19s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
43s{color} | {color:green} branch-2.1 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
39s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}  
9m 15s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4 
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m  
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
30s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}110m 
29s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
26s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}151m  6s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:42ca976 |
| JIRA Issue | HBASE-21271 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12943737/HBASE-21271.branch-2.1.002.patch
 |
| Optional Tests |  dupname  asflicense  javac  javadoc  unit  findbugs  
shadedjars  hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 52dc1e6e485d 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 
10:45:36 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | branch-2.1 / 72af27b8c9 |
| maven | version: Apache Maven 3.5.4 
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/14679/testReport/ |
| Max. process+thread count | 4904 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console output | 
https://bui

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-10 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644878#comment-16644878
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.1
[build #442 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/442/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/442//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/442//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/442//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642813#comment-16642813
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.0
[build #923 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/923/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/923//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/923//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/923//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642649#comment-16642649
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.1
[build #435 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/435/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/435//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/435//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/435//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread Hudson (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642569#comment-16642569
 ] 

Hudson commented on HBASE-21271:


Results for branch branch-2.0
[build #922 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread stack (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642126#comment-16642126
 ] 

stack commented on HBASE-21271:
---

I applied this to branch-2.0, branch-2.1, but then reverted it. Let me get some 
more mileage on this patch before applying. Need to figure out if needed in 
branch-2 also.

> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread Allan Yang (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641509#comment-16641509
 ] 

Allan Yang commented on HBASE-21271:


I'm OK with this, throwing an UnsupportedOperationException is too violent...

> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-08 Thread stack (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641489#comment-16641489
 ] 

stack commented on HBASE-21271:
---

[~allan163] u good w this sir?

> [amv2] Don't throw UnsupportedOperationException when rollback called on 
> Assign/Unassign; spiral of death
> -
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
>  Issue Type: Bug
>  Components: amv2
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a 
> subprocedure of an Enable/Disable and for whatever reason the parent decides 
> it needs to rollback -- can't get an entity lock -- it will ask the 
> subprocedures to rollback. UP and AP don't support rollback on all steps. For 
> steps where not supported, we have been throwing a 
> UnsupportedOperationException The Framework reschedules the rollback. And 
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until 
> we to to 2.2 when AP/UP go away).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

2018-10-05 Thread Hadoop QA (JIRA)



[ 
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639699#comment-16639699
 ] 

Hadoop QA commented on HBASE-21271:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
27s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}  
0m  0s{color} | {color:orange} The patch doesn't appear to include any new or 
modified tests. Please justify why no new tests are needed for this patch. Also 
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} branch-2.1 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
44s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
50s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
10s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
22s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m  
5s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
39s{color} | {color:green} branch-2.1 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
23s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}  
8m 12s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4 
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m  
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
28s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}221m 24s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
26s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}259m 20s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAdmin1 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:42ca976 |
| JIRA Issue | HBASE-21271 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12942499/HBASE-21271.branch-2.1.001.patch
 |
| Optional Tests |  dupname  asflicense  javac  javadoc  unit  findbugs  
shadedjars  hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux a183d1c1cc6f 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 
07:31:43 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | branch-2.1 / 9d34b4581c |
| maven | version: Apache Maven 3.5.4 
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/14576/artifact/patchprocess/patch-unit-hbase-server.txt
 |
|  Test Results | 
https://builds

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

[jira] [Commented] (HBASE-21271) [amv2] Don't throw UnsupportedOperationException when rollback called on Assign/Unassign; spiral of death

11 matches

Site Navigation

Mail list logo

Footer information