[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131079#comment-16131079
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBASE-14070.HLC #233 (See
[https://builds.apache.org/job/HBASE-14070.HLC/233/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 9a1661832d5f515df2addf706d0e249a8a2bb8cb)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckReplicas.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104506#comment-16104506
]
Esteban Gutierrez commented on HBASE-18362:
---
Good catch [~anoop.hbase], it should be 1.4.0. Fixing.
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME => 't1,,1500931787511.dc471b6d9c0c2c451ee4c6d134
> . e50ccc.', STARTKEY => '',
> ENDKEY => 'r'}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitB,
> timestamp=1500931787651,
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104446#comment-16104446
]
Anoop Sam John commented on HBASE-18362:
The fix version is 1.4.1 or 1.4.0 ?
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME => 't1,,1500931787511.dc471b6d9c0c2c451ee4c6d134
> . e50ccc.', STARTKEY => '',
> ENDKEY => 'r'}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitB,
> timestamp=1500931787651, value={ENCODED =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104208#comment-16104208
]
Hudson commented on HBASE-18362:
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #222 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/222/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev c23b7c9c80d7663741b598f221cca8b4eb74033c)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104171#comment-16104171
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3446 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3446/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 9a1661832d5f515df2addf706d0e249a8a2bb8cb)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckReplicas.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104085#comment-16104085
]
Hudson commented on HBASE-18362:
SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #168 (See
[https://builds.apache.org/job/HBase-1.2-JDK8/168/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 34120e896956c3e08ff51a7cd12013888f9bf93e)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104080#comment-16104080
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBase-1.4 #824 (See
[https://builds.apache.org/job/HBase-1.4/824/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev e662d04321f2c4cec29a775a220752a50168026d)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16104035#comment-16104035
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBase-2.0 #245 (See
[https://builds.apache.org/job/HBase-2.0/245/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 75789048c13d925d9ee9b67ad8b8dc356e7547ff)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckReplicas.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103953#comment-16103953
]
Hudson commented on HBASE-18362:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #145 (See
[https://builds.apache.org/job/HBase-1.3-IT/145/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev c23b7c9c80d7663741b598f221cca8b4eb74033c)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103938#comment-16103938
]
Hudson commented on HBASE-18362:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #906 (See
[https://builds.apache.org/job/HBase-1.2-IT/906/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 34120e896956c3e08ff51a7cd12013888f9bf93e)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103936#comment-16103936
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #207 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/207/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev c23b7c9c80d7663741b598f221cca8b4eb74033c)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103931#comment-16103931
]
Hudson commented on HBASE-18362:
FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #172 (See
[https://builds.apache.org/job/HBase-1.2-JDK7/172/])
HBASE-18362 hbck should not report split replica parent region from meta
(esteban: rev 34120e896956c3e08ff51a7cd12013888f9bf93e)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 3.0.0, 1.3.2, 1.4.1, 1.2.7
>
> Attachments: HBASE-18362.001.patch, HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103864#comment-16103864
]
Esteban Gutierrez commented on HBASE-18362:
---
I will go ahead and commit since the change is not related to the failure.
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Attachments: HBASE-18362-branch-1-v001.patch,
> HBASE-18362-branch-1-v002.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME => 't1,,1500931787511.dc471b6d9c0c2c451ee4c6d134
> . e50ccc.', STARTKEY => '',
> ENDKEY => 'r'}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitB,
> timestamp=1500931787651, value={ENCODED => d86fbd197ca1073e763cb811705587ec,
> NAME =>
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101237#comment-16101237
]
Hadoop QA commented on HBASE-18362:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
28s{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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
4s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
33s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
36s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
57s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
31s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{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}
15m 43s{color} | {color:green} The patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}107m 3s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}137m 38s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestSCVFWithMiniCluster |
| | hadoop.hbase.master.TestAssignmentListener |
| |
hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint |
| | hadoop.hbase.client.TestReplicasClient |
| Timed out junit tests | org.apache.hadoop.hbase.security.access.TestCellACLs |
| | org.apache.hadoop.hbase.client.TestTableSnapshotScanner |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:6f1cc2c |
| JIRA Issue | HBASE-18362 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878945/HBASE-18362-branch-1-v002.patch
|
| Optional Tests | asflicense
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100175#comment-16100175
]
Esteban Gutierrez commented on HBASE-18362:
---
Test failures don't seem to be related. I will dig into
TestReplicasClient.testCancelOfMultiGet but it has been flaky for a long time.
Otherwise, if there are no further comments I will go a head and commit.
> hbck should not report split replica parent region from meta as errors
> ---
>
> Key: HBASE-18362
> URL: https://issues.apache.org/jira/browse/HBASE-18362
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 1.4.0, 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Attachments: HBASE-18362-branch-1-v001.patch
>
>
> As described in HBASE-18247, replica region shows up as key in meta table. We
> need to find out the code/logic introducing the issue. I suspected that it
> was introduced by hbck, but last round of code review did not find anything.
> Create jira to track this effort.
> Before Catalog Janitor cleans up the split parent region from meta, hbck is
> reporting split replica parent regions as errors and if -fixSplitParents is
> used, the replica parent region will show up as key in meta table. It needs
> to be avoided.
> {code}
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:regioninfo,
> timestamp=1500931787651, value={ENCODED => e10212c467b78104c911ea06c102ece0,
> NAME => 't1,,1500931628959.e10212c467b78104c911ea
> . 06c102ece0.', STARTKEY =>
> '', ENDKEY => '', OFFLINE => true, SPLIT => true}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen, timestamp=1500931742552,
> value=\x00\x00\x00\x00\x00\x00\x00\x05
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:seqnumDuringOpen_0001, timestamp=1500931742492,
> value=\x00\x00\x00\x00\x00\x00\x00\x02
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server,
> timestamp=1500931742552, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:server_0001,
> timestamp=1500931742492, value=dhcp-172-16-1-203.pa.cloudera.com:61099
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode, timestamp=1500931742552, value=1500931737158
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
> column=info:serverstartcode_0001, timestamp=1500931742492,
> value=\x00\x00\x01]v\x80\xC6F
>
> .
>
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0 column=info:splitA,
> timestamp=1500931787651, value={ENCODED => dc471b6d9c0c2c451ee4c6d134e50ccc,
> NAME => 't1,,1500931787511.dc471b6d9c0c2c451ee4c6d134
> . e50ccc.', STARTKEY => '',
> ENDKEY => 'r'}
>
> t1,,1500931628959.e10212c467b78104c911ea06c102ece0
[jira] [Commented] (HBASE-18362) hbck should not report split replica parent region from meta as errors
[
https://issues.apache.org/jira/browse/HBASE-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099627#comment-16099627
]
Hadoop QA commented on HBASE-18362:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 19m
7s{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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
26s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
41s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
38s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
1s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
25s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
5s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
41s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
37s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s{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}
17m 45s{color} | {color:green} The patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
30s{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 with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}104m 20s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}162m 31s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.TestMasterFailover |
| | hadoop.hbase.master.balancer.TestStochasticLoadBalancer |
| | hadoop.hbase.regionserver.TestRSKilledWhenInitializing |
| | hadoop.hbase.client.TestReplicasClient |
| | hadoop.hbase.coprocessor.TestRowProcessorEndpoint |
| | hadoop.hbase.client.TestClientScannerRPCTimeout |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.13.1 Server=1.13.1 Image:yetus/hbase:6f1cc2c |
| JIRA Issue | HBASE-18362 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878706/HBASE-18362-branch-1-v001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti
