You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2012/10/23 20:39:13 UTC
[jira] [Created] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
stack created HBASE-7037:
----------------------------
Summary: ReplicationPeer logs at WARN level aborting server instead of at FATAL
Key: HBASE-7037
URL: https://issues.apache.org/jira/browse/HBASE-7037
Project: HBase
Issue Type: Bug
Reporter: stack
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-7037:
-------------------------
Resolution: Fixed
Fix Version/s: 0.96.0
0.94.3
Assignee: liang xie
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and 0.94 branch. Thanks for the patch Liang.
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Assignee: liang xie
> Labels: noob
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482947#comment-13482947 ]
Hadoop QA commented on HBASE-7037:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12550585/HBASE-7037.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. 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:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 82 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSide
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3133//console
This message is automatically generated.
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Labels: noob
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483173#comment-13483173 ]
Hudson commented on HBASE-7037:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #233 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/233/])
HBASE-7037 ReplicationPeer logs at WARN level aborting server instead of at FATAL (Revision 1401563)
Result = FAILURE
stack :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeer.java
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Assignee: liang xie
> Labels: noob
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "liang xie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liang xie updated HBASE-7037:
-----------------------------
Attachment: HBASE-7037.txt
just one line change:)
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Labels: noob
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490382#comment-13490382 ]
Hudson commented on HBASE-7037:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #9 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/9/])
HBASE-7037 ReplicationPeer logs at WARN level aborting server instead of at FATAL (Revision 1401564)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeer.java
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Assignee: liang xie
> Labels: noob
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-7037:
-------------------------
Component/s: Replication
Labels: noob (was: )
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Labels: noob
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "liang xie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liang xie updated HBASE-7037:
-----------------------------
Status: Patch Available (was: Open)
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Labels: noob
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483077#comment-13483077 ]
Hudson commented on HBASE-7037:
-------------------------------
Integrated in HBase-0.94 #552 (See [https://builds.apache.org/job/HBase-0.94/552/])
HBASE-7037 ReplicationPeer logs at WARN level aborting server instead of at FATAL (Revision 1401564)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeer.java
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Assignee: liang xie
> Labels: noob
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7037) ReplicationPeer logs at WARN level
aborting server instead of at FATAL
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483087#comment-13483087 ]
Hudson commented on HBASE-7037:
-------------------------------
Integrated in HBase-TRUNK #3480 (See [https://builds.apache.org/job/HBase-TRUNK/3480/])
HBASE-7037 ReplicationPeer logs at WARN level aborting server instead of at FATAL (Revision 1401563)
Result = FAILURE
stack :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeer.java
> ReplicationPeer logs at WARN level aborting server instead of at FATAL
> ----------------------------------------------------------------------
>
> Key: HBASE-7037
> URL: https://issues.apache.org/jira/browse/HBASE-7037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: stack
> Assignee: liang xie
> Labels: noob
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-7037.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira