[OOZIE-3467] Migrate from com.google.common.base.Stopwatch

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 5.2.0
• Assignee: Andras Salamon
• Reporter: Andras Salamon
• Created: 08/Apr/19 09:30
• Updated: 09/Dec/19 08:53
• Resolved: 09/Apr/19 10:19

Description

OOZIE-1826 created JvmPauseMonitorService which uses Guava's stopwatch. The implementation was heavily inspired by HADOOP-9618. Guava changed the StopWatch class in a way that we either create a version which is compatible in the old (Guava 11) or the new (Guava 27) interface. To make the code Guava version independent we should not use this class anymore. Hadoop also replaced this class in HADOOP-11032.

We don't really need nanosecond accuracy here, we only read milliseconds from the stopwatch and the default thresholds are 1 second (oozie.service.JvmPauseMonitorService.info-threshold.ms = 1000ms) and 10 seconds (oozie.service.JvmPauseMonitorService.warn-threshold.ms = 10 000ms) so even millisecond is a bit overkill. We could just use System.currentTimeMillis().

Issue Links

• relates to: OOZIE-3418 Upgrade to Guava 27