[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877745#comment-15877745 ] Hudson commented on HBASE-17675: FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #109 (See [https://builds.apache.org/job/HBase-1.3-JDK7/109/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 00d79eb9fbc34b36b2c85a6d834106c8b69525c9) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877738#comment-15877738 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1930 (See [https://builds.apache.org/job/HBase-1.1-JDK8/1930/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 7a196b7fb89bcf5bb83a8110e78575ab18a53012) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877710#comment-15877710 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2549 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2549/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c0750de54276cf19a35feb6351c71b8dea360b7) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877646#comment-15877646 ] Hudson commented on HBASE-17675: FAILURE: Integrated in Jenkins build HBase-1.2-IT #602 (See [https://builds.apache.org/job/HBase-1.2-IT/602/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c7e96a6fde2fad85483631032c7526a96e49f22) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877612#comment-15877612 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #835 (See [https://builds.apache.org/job/HBase-1.3-IT/835/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c7e96a6fde2fad85483631032c7526a96e49f22) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877565#comment-15877565 ] Hudson commented on HBASE-17675: FAILURE: Integrated in Jenkins build HBase-1.1-JDK7 #1846 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1846/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 7a196b7fb89bcf5bb83a8110e78575ab18a53012) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877554#comment-15877554 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.4 #638 (See [https://builds.apache.org/job/HBase-1.4/638/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 27a8aa99d913899752cbbf48bb4b639d299fca83) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877545#comment-15877545 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #104 (See [https://builds.apache.org/job/HBase-1.2-JDK7/104/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c7e96a6fde2fad85483631032c7526a96e49f22) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877529#comment-15877529 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #119 (See [https://builds.apache.org/job/HBase-1.3-JDK8/119/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 00d79eb9fbc34b36b2c85a6d834106c8b69525c9) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877499#comment-15877499 ] Hudson commented on HBASE-17675: SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #97 (See [https://builds.apache.org/job/HBase-1.2-JDK8/97/]) HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c7e96a6fde2fad85483631032c7526a96e49f22) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[
https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877337#comment-15877337
]
Hadoop QA commented on HBASE-17675:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 25s
{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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
34s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
47s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
46s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
45s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
47s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {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}
31m 56s {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} 2m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 102m 5s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
15s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 147m 48s {color}
| {color:black} {color} |
\\
\\
|| 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/12853826/HBASE-17675.patch |
| JIRA Issue | HBASE-17675 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux e7f9393d742a 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 / d7ffa00 |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5788/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5788/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> ReplicationEndpoint should choose new sinks if a SaslException occurs
> --
>
> Key: HBASE-17675
> URL: https://issues.apache.org/jira/browse/HBASE-17675
> Project: HBase
> Issue Type: Bug
>Reporter: churro morales
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876995#comment-15876995 ] churro morales commented on HBASE-17675: thanks [~apurtell] > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.3.1 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876988#comment-15876988 ] Andrew Purtell commented on HBASE-17675: +1 > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.3.1 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
[ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876989#comment-15876989 ] Andrew Purtell commented on HBASE-17675: I will commit this later today unless objection. Thanks [~churromorales] > ReplicationEndpoint should choose new sinks if a SaslException occurs > -- > > Key: HBASE-17675 > URL: https://issues.apache.org/jira/browse/HBASE-17675 > Project: HBase > Issue Type: Bug >Reporter: churro morales >Assignee: churro morales > Fix For: 2.0.0, 1.3.1 > > Attachments: HBASE-17675.patch > > > We had an issue where a regionserver on our destination side failed to > refresh the keytabs. The source side's replication got stuck because the > HBaseInterClusterReplicationEndpoint only chooses new sinks if there happens > to be a ConnectException but the SaslException is an IOException, which does > not choose new sinks. > I'll put up a patch to check this exception and choose new sinks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
