[FLINK-4145] JmxReporterTest fails due to port conflicts

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: Runtime / Metrics, Runtime / Task
• Labels: test-stability
• Assignee: Chesnay Schepler
• Reporter: Ufuk Celebi
• Created: 03/Jul/16 14:07
• Updated: 05/Jul/16 07:50
• Resolved: 05/Jul/16 07:50

Description

I saw multiple failures of the JmxReporterTest most likely due to a port conflicts. The test relies on the default JMX reporter port range, which spans 5 ports. Running on Travis with multiple concurrent builds and bad timings, this can lead to port conflicts.

Some example failed runs:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/141999066/log.txt (one out of 5 jobs failed)

https://travis-ci.org/uce/flink/builds/141917901 (all 5 jobs failed)

I propose to take the fork number into account (like the forkable Flink testing cluster) and configure a larger port range.

Issue Links

• links to: GitHub Pull Request #2193