[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-17705:


FAILURE: Integrated in Jenkins build HBASE-14070.HLC #69 (See 
[https://builds.apache.org/job/HBASE-14070.HLC/69/])
HBASE-17705 Procedure execution must fail fast if procedure is not (tedyu: rev 
7d007eac98daef8d41ac1d8adf397967fa2919fd)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerImpl.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java
* (add) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestFastFailOnProcedureNotRegistered.java


> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-11 Thread Hudson (JIRA)

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

Hudson commented on HBASE-17705:


FAILURE: Integrated in Jenkins build HBase-2.0 #151 (See 
[https://builds.apache.org/job/HBase-2.0/151/])
HBASE-17705 Procedure execution must fail fast if procedure is not (tedyu: rev 
5d7dfa4d1dfc290b0eed4f37b68c4bbb9aff7a2b)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerImpl.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java
* (add) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestFastFailOnProcedureNotRegistered.java


> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-17705:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3351 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3351/])
HBASE-17705 Procedure execution must fail fast if procedure is not (tedyu: rev 
7d007eac98daef8d41ac1d8adf397967fa2919fd)
* (add) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestFastFailOnProcedureNotRegistered.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerImpl.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java


> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-07 Thread Vladimir Rodionov (JIRA)

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

Vladimir Rodionov commented on HBASE-17705:
---

These test failures are not related to the patch. I think patch is ready.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-06 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-17705:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
51s{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
51s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
10s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  2m 
27s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  7m  
3s{color} | {color:red} hbase-server in master has 10 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
46s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
41s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  2m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
48s{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} hadoopcheck {color} | {color:green} 
72m 27s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  9m  
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  4m 
20s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}344m 54s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  1m 
12s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}469m 23s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionReplicaFailover |
|   | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
|   | hadoop.hbase.security.access.TestCoprocessorWhitelistMasterObserver |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-17705 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12875830/HBASE-17705.v3.patch |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux eb9654242c35 4.8.3-std-1 #1 SMP Fri Oct 21 11:15:43 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | master / b715091 |
| Default 

[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread Vladimir Rodionov (JIRA)

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

Vladimir Rodionov commented on HBASE-17705:
---

{quote}
IOE is our base exception so catching it is a little indiscriminating. Can the 
test have more precision? Catch DoNotRetryIOE at least or some such?
{quote}

v3 catches DNRIOE.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread stack (JIRA)

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

stack commented on HBASE-17705:
---

IOE is our base exception so catching it is a little indiscriminating. Can the 
test have more precision? Catch DoNotRetryIOE at least or some such? Otherwise, 
nice test and patch looks good.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v2.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-17705:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  2m 17s{color} 
| {color:red} HBASE-17705 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-17705 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12855223/HBASE-17705.v1.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/7525/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch, HBASE-17705.v2.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread Ted Yu (JIRA)

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

Ted Yu commented on HBASE-17705:


lgtm, pending QA.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch, HBASE-17705.v2.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread Vladimir Rodionov (JIRA)

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

Vladimir Rodionov commented on HBASE-17705:
---

ping [~tedyu]

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch, HBASE-17705.v2.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-07-05 Thread Vladimir Rodionov (JIRA)

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

Vladimir Rodionov commented on HBASE-17705:
---

Test is coming.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-06-29 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-17705:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  1m 43s{color} 
| {color:red} HBASE-17705 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-17705 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12855223/HBASE-17705.v1.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/7401/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-06-29 Thread stack (JIRA)

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

stack commented on HBASE-17705:
---

Looks good. How about a test? Thanks.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-03-07 Thread Ted Yu (JIRA)

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

Ted Yu commented on HBASE-17705:


lgtm

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-02-28 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-17705:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s 
{color} | {color:blue} Docker mode activated. {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:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s 
{color} | {color:red} 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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 27s 
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 
8s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 51s 
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
44s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 
27s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s 
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 12s 
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 52s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
23s {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} hadoopcheck {color} | {color:green} 
30m 12s {color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m 
21s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 53s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 19s 
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 98m 0s {color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
27s {color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 147m 59s {color} 
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestHCM |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12855223/HBASE-17705.v1.patch |
| JIRA Issue | HBASE-17705 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux 33cba760a955 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 
09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 4a5eba5 |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/5881/artifact/patchprocess/patch-unit-hbase-server.txt
 |
| unit test logs |  

[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-02-28 Thread stack (JIRA)

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

stack commented on HBASE-17705:
---

Excellent [~vrodionov]. Any chance of a test? You think this for master branch 
only?

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-17705.v1.patch
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered

2017-02-28 Thread stack (JIRA)

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

stack commented on HBASE-17705:
---

Made this a blocker because this long-running issue that manifests variously. 
The operator/user is left stumped by a hanging connection that is silent on 
what it is doing; baffling.

> Procedure execution must fail fast if procedure is not registered
> -
>
> Key: HBASE-17705
> URL: https://issues.apache.org/jira/browse/HBASE-17705
> Project: HBase
>  Issue Type: Bug
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
>Priority: Blocker
> Fix For: 2.0.0
>
>
> The issue was discovered during backup testing and described here:
> https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712
> If procedure is not registered, client will be retrying until max attempts 
> reached. The Master should throw DoNotRetryIOException and client RPC should 
> handle this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)