[
https://issues.apache.org/jira/browse/HBASE-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429670#comment-16429670
]
Duo Zhang commented on HBASE-20362:
-----------------------------------
Let me commit to see if it helps since the pre commit will not run the flaky
tests...
> TestMasterShutdown.testMasterShutdownBeforeStartingAnyRegionServer is flaky
> ---------------------------------------------------------------------------
>
> Key: HBASE-20362
> URL: https://issues.apache.org/jira/browse/HBASE-20362
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20362.patch
>
>
> {code}
> Thread shutdownThread = new Thread("Shutdown-Thread") {
> @Override
> public void run() {
> LOG.info("Before call to shutdown master");
> try {
> try (Connection connection =
> ConnectionFactory.createConnection(util.getConfiguration())) {
> try (Admin admin = connection.getAdmin()) {
> admin.shutdown();
> }
> }
> LOG.info("After call to shutdown master");
> cluster.waitOnMaster(MASTER_INDEX);
> } catch (Exception e) {
> }
> }
> };
> {code}
> https://builds.apache.org/job/HBASE-Flaky-Tests/28970/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.master.TestMasterShutdown-output.txt
> In the output for a failed running, we only have 'Before call to shutdown
> master' but no 'After call to shutdown master', so I think there must be
> something wrong when calling admin.shutdown, but in the catch block below we
> just ignore the exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
