You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Cameron Lee (Jira)" <ji...@apache.org> on 2020/03/27 01:07:00 UTC

[jira] [Updated] (SAMZA-2496) TestContainerHeartbeatMonitor does not properly stop the ContainerHeartbeatMonitor

     [ https://issues.apache.org/jira/browse/SAMZA-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Lee updated SAMZA-2496:
-------------------------------
    Summary: TestContainerHeartbeatMonitor does not properly stop the ContainerHeartbeatMonitor  (was: Clean up ContainerHeartbeatMonitor stop flow)

> TestContainerHeartbeatMonitor does not properly stop the ContainerHeartbeatMonitor
> ----------------------------------------------------------------------------------
>
>                 Key: SAMZA-2496
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2496
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Cameron Lee
>            Assignee: Cameron Lee
>            Priority: Major
>
> TestContainerHeartbeatMonitor does not properly stop the ContainerHeartbeatMonitor, so after 2 minutes, it can do a force shutdown of the whole test process if the test process is still alive.
> The force shutdown task is set up using ScheduledExecutorService.schedule. ScheduledExecutorService.shutdown does not seem to cancel tasks created using the "schedule" method. It seems reasonable to use ScheduledExecutorService.shutdownNow when calling ContainerHeartbeatMonitor.stop, which will also cancel the force shutdown task.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)