[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340754#comment-15340754
]
Hudson commented on HBASE-16059:
FAILURE: Integrated in HBase-Trunk_matrix #1084 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1084/])
HBASE-16059 Region normalizer fails to trigger merge action where one of
(tedyu: rev be56b5ae7119bc58d4c755974f89f5eabc70a43e)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/master/normalizer/SimpleRegionNormalizer.java
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340569#comment-15340569
]
Hudson commented on HBASE-16059:
FAILURE: Integrated in HBase-1.4 #229 (See
[https://builds.apache.org/job/HBase-1.4/229/])
HBASE-16059 Region normalizer fails to trigger merge action where one of
(tedyu: rev 78f52628960547f4717621e0863456fe1af0cda6)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/master/normalizer/SimpleRegionNormalizer.java
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1533#comment-1533
]
Stephen Yuan Jiang commented on HBASE-16059:
+1. The patch looks good to me.
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339998#comment-15339998
]
Stephen Yuan Jiang commented on HBASE-16059:
In the future, we probably could improve the current approach - a lot of
customers using pre-split (and I see a lot of books recommended that). Agree
that this would be a different task
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339502#comment-15339502
]
Ted Yu commented on HBASE-16059:
The current code doesn't adhere to the pre-split regions either.
Suppose adjacent regions R1 and R2 are result of pre-splitting. They receive
some writes but the sum of their sizes is lower than the average region
size. They would be merged according to current logic.
To preserve pre-split regions, we need some other tracking mechanism.
I suggest adding such tracking in other JIRA(s).
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15338892#comment-15338892
]
Stephen Yuan Jiang commented on HBASE-16059:
[~tedyu], question on the change: in the case of pre-split, we don't want to
run region normalizer to merge regions. Will your change break this assumption?
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337325#comment-15337325
]
Ted Yu commented on HBASE-16059:
{code}
Failed tests:
TestMultithreadedTableMapper.testMultithreadedTableMapper:132->runTestOnTable:155
null
Flaked tests:
org.apache.hadoop.hbase.TestPartialResultsFromClientSide.testExpectedNumberOfCellsPerPartialResult(org.apache.hadoop.hbase.TestPartialResultsFromClientSide)
Run 1:
TestPartialResultsFromClientSide.testExpectedNumberOfCellsPerPartialResult »
TableNotFound
Run 2: PASS
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient.testRestoreSchemaChange(org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient)
Run 1:
TestRestoreSnapshotFromClient.testRestoreSchemaChange:207->countRows:321 »
Runtime
Run 2: PASS
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles.testRegionCrossingHFileSplitRowBloom(org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles)
Run 1:
TestLoadIncrementalHFiles.testRegionCrossingHFileSplitRowBloom:192->testRegionCrossingHFileSplit:227->runTest:259->runTest:269->runTest:295
» ScannerTimeout
Run 2: PASS
org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan2.testScanYYYToEmpty(org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan2)
Run 1:
TestTableInputFormatScan2.testScanYYYToEmpty:97->TestTableInputFormatScanBase.testScan:240
» TableNotFound
Run 2: PASS
org.apache.hadoop.hbase.regionserver.TestScannerRetriableFailure.testFaultyScanner(org.apache.hadoop.hbase.regionserver.TestScannerRetriableFailure)
Run 1: TestScannerRetriableFailure.testFaultyScanner:113->checkTableRows:150
» ScannerTimeout
Run 2: PASS
org.apache.hadoop.hbase.regionserver.wal.TestAsyncLogRollPeriod.testWithEdits(org.apache.hadoop.hbase.regionserver.wal.TestAsyncLogRollPeriod)
Run 1:
TestAsyncLogRollPeriod>AbstractTestLogRollPeriod.testWithEdits:124->Object.wait:-2
» TestTimedOut
Run 2: PASS
org.apache.hadoop.hbase.regionserver.wal.TestAsyncLogRolling.testLogRollOnDatanodeDeath(org.apache.hadoop.hbase.regionserver.wal.TestAsyncLogRolling)
Run 1: TestAsyncLogRolling.testLogRollOnDatanodeDeath:63 expected:<1> but
was:<0>
Run 2: PASS
Tests run: 1900, Failures: 1, Errors: 0, Skipped: 44, Flakes: 7
{code}
Failed test was not related to the patch.
> Region normalizer fails to trigger merge action where one of the regions is
> empty
> -
>
> Key: HBASE-16059
> URL: https://issues.apache.org/jira/browse/HBASE-16059
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Romil Choksi
>Assignee: Ted Yu
> Labels: normalization
> Fix For: 2.0.0
>
> Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting with
> key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists - 1) STARTKEY =>
> ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’
> - Turn on normalization, verify normalization switch is enabled and that
> normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don’t exist anymore 1) STARTKEY
> => ‘' ENDKEY => ’1’ 2) STARTKEY => ’1’ ENDKEY => ’3’, but instead a new
> region is created with STARTKEY => ’’ ENDKEY => ’3’
> The test now fails, with the last step failing at assertion.
> Looking into the Master log, I see that normalization plan was computed for
> the test table but it decides that no normalization is needed for the test
> table, and that the regions look good.
> {code:title = Master.log}
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Computing normalization plan for table:
> table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, total aggregated
> regions size: 13
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, average region
> size: 2.6
> 2016-06-17 00:41:46,896 DEBUG
> [B.defaultRpcServer.handler=4,queue=1,port=2]
> normalizer.SimpleRegionNormalizer: No normalization needed, regions look good
> for table: table_zrof6ea383
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16059) Region normalizer fails to trigger merge action where one of the regions is empty
[
https://issues.apache.org/jira/browse/HBASE-16059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337224#comment-15337224
]
Hadoop QA commented on HBASE-16059:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m 1s
{color} | {color:blue} The patch file was not named according to hbase's naming
conventions. Please see
https://yetus.apache.org/documentation/0.2.1/precommit-patchnames for
instructions. {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} 4m
4s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 56s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 59s
{color} | {color:green} master passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
20s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
35s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 41s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 44s
{color} | {color:green} master passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
57s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 59s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 59s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 54s
{color} | {color:green} the patch passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 54s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 24s {color} | {color:green} 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
46s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 43s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 45s
{color} | {color:green} the patch passed with JDK v1.7.0_80 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 123m 45s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
55s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 179m 38s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | org.apache.hadoop.hbase.TestHBaseTestingUtility |
| | org.apache.hadoop.hbase.TestZooKeeper |
| | org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot |
| | org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildBase |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
