[jira] [Assigned] (HBASE-17960) IntegrationTestReplication fails in successive runs due to lack of appropriate cleanup
[ https://issues.apache.org/jira/browse/HBASE-17960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reassigned HBASE-17960: -- Assignee: (was: Ashu Pachauri) > IntegrationTestReplication fails in successive runs due to lack of > appropriate cleanup > -- > > Key: HBASE-17960 > URL: https://issues.apache.org/jira/browse/HBASE-17960 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Ashu Pachauri >Priority: Major > Fix For: 2.0.0, 3.0.0, 1.3.2, 1.5.0, 1.4.3 > > > The way ITR works right now is that it adds a peer named 'TestPeer' for the > replication destination cluster. The name of the peer is same across runs. > Also, it removes the peer in the beginning of each run. However, it does not > wait for the queues corresponding to the peer to get cleaned up (which is an > asynchronous operation and can take 10s of seconds). This causes the next run > to fail and so on. > The test setup should wait for a non-trivial amount of time to cleanup the > queues corresponding to the peer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-17960) IntegrationTestReplication fails in successive runs due to lack of appropriate cleanup
[ https://issues.apache.org/jira/browse/HBASE-17960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashu Pachauri reassigned HBASE-17960: - Assignee: Ashu Pachauri > IntegrationTestReplication fails in successive runs due to lack of > appropriate cleanup > -- > > Key: HBASE-17960 > URL: https://issues.apache.org/jira/browse/HBASE-17960 > Project: HBase > Issue Type: Bug > Components: integration tests >Reporter: Ashu Pachauri >Assignee: Ashu Pachauri > > The way ITR works right now is that it adds a peer named 'TestPeer' for the > replication destination cluster. The name of the peer is same across runs. > Also, it removes the peer in the beginning of each run. However, it does not > wait for the queues corresponding to the peer to get cleaned up (which is an > asynchronous operation and can take 10s of seconds). This causes the next run > to fail and so on. > The test setup should wait for a non-trivial amount of time to cleanup the > queues corresponding to the peer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
