[jira] [Updated] (HBASE-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6714: - Fix Version/s: (was: 0.95.0) 0.94.2 Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by Lars Hofhansl) TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: Replication, test Affects Versions: 0.92.0, 0.94.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Priority: Minor Fix For: 0.94.2 Attachments: HBase-6714-v1.patch java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6714: - Resolution: Fixed Fix Version/s: 0.96.0 0.94.2 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to 0.94 and to trunk. Thanks for the patch Himanshu. TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: Replication, test Affects Versions: 0.92.0, 0.94.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Priority: Minor Fix For: 0.94.2, 0.96.0 Attachments: HBase-6714-v1.patch java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-6714: --- Description: java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. was:TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: replication, test Affects Versions: 0.92.0, 0.94.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-6714: --- Attachment: HBase-6714-v1.patch Passed locally in a loop of 15; enqueued jenkins. TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: replication, test Affects Versions: 0.92.0, 0.94.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Attachments: HBase-6714-v1.patch java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-6714: --- Status: Patch Available (was: Open) TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: replication, test Affects Versions: 0.94.0, 0.92.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Attachments: HBase-6714-v1.patch java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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-6714) TestMultiSlaveReplication#testMultiSlaveReplication may fail
[ https://issues.apache.org/jira/browse/HBASE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-6714: --- Priority: Minor (was: Major) TestMultiSlaveReplication#testMultiSlaveReplication may fail Key: HBASE-6714 URL: https://issues.apache.org/jira/browse/HBASE-6714 Project: HBase Issue Type: Bug Components: replication, test Affects Versions: 0.92.0, 0.94.0 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Priority: Minor Attachments: HBase-6714-v1.patch java.lang.AssertionError: expected:1 but was:0 at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.checkRow(TestMultiSlaveReplication.java:203) at org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication(TestMultiSlaveReplication.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) TestMultiSlaveReplication-testMultiSlaveReplication failed in our local build citing that row was not replicated to second peer. This is because after inserting row, log is rolled and we look for row2 in both the clusters and then we check for existence of row in both clusters. Meanwhile, Replication thread was sleeping for the second cluster and Row row2 is not present in the second cluster from the very beginning. So, the row2 existence check succeeds and control move on to find row in both clusters where it fails for the second cluster. -- 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
