[ https://issues.apache.org/jira/browse/HBASE-25478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265788#comment-17265788 ]
Viraj Jasani edited comment on HBASE-25478 at 1/15/21, 7:51 AM: ---------------------------------------------------------------- It seems we have seen flakies with ReplicationException as same peerId can be used by multiple tests. Hence, it is focusing on ReplicationException. {code:java} catch (IOException e) { if (e.getCause() instanceof ReplicationException) { continueToRetry = true; tries++; Uninterruptibles.sleepUninterruptibly(1, TimeUnit.SECONDS); } } {code} Does it sound good [~stack]? was (Author: vjasani): It seems we have seen flakies with ReplicationException as same peerId can be used by multiple tests. Hence, it is focusing on ReplicationException. {code:java} catch (IOException e) { if (e.getCause() instanceof ReplicationException) { continueToRetry = true; tries++; Uninterruptibles.sleepUninterruptibly(1, TimeUnit.SECONDS); } } {code} Does it sound good [~stack]? > Implement retries when enabling tables in TestRegionReplicaReplicationEndpoint > ------------------------------------------------------------------------------ > > Key: HBASE-25478 > URL: https://issues.apache.org/jira/browse/HBASE-25478 > Project: HBase > Issue Type: Bug > Reporter: Christine Feng > Priority: Minor > > When a table from a previous test is too slow to close, it can cause problems > for subsequent tests. Implementing a retry-and-wait function in this test > class during table enablement will prevent issues where a single peerID is > being used by two tests at once. -- This message was sent by Atlassian Jira (v8.3.4#803005)