Fix TestNameNodeMetrics

Description

TestNameNodeMetrics regularly fail because:

  1. the fist block reporting may take a little time and testSyncAndBlockReportMetric is getting the metrics before it is done

  2. updateMetrics being equal to exactly equal to dfs.namenode.replication.interval can result in a race condition making that the metrics get updated just after the test get them instead of just before.

Status

Assignee

Gautier Berthou

Reporter

Gautier Berthou

Labels

None

Fix versions

Priority

Medium