[
https://issues.apache.org/jira/browse/SAMZA-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shanthoosh Venkataraman updated SAMZA-1390:
-------------------------------------------
Description:
Observed in LI production that samza-rest jvm process doesn’t stop after main
thread death(due to jetty server failures) since non-deamon threads spawned for
`SamzaMonitorService` are alive.
* This affects samza-rest jvm process lifecycle management. To fix this,
plugging in ThreadFactory which sets Thread name format & marks them as daemon.
* Shutdown executorService in finally block (in case of any exception & also
during normal exit).
was:
Observed in LI production that samza-rest jvm process doesn’t stop after main
thread death(due to jetty server failures) since non-deamon threads spawned for
`SamzaMonitorService` are alive.
This affects samza-rest jvm process lifecycle management. To fix this, plugging
in ThreadFactory which sets Thread name format & marks them as daemon.
> Update SamzaMonitorService to spawn deamon threads.
> ---------------------------------------------------
>
> Key: SAMZA-1390
> URL: https://issues.apache.org/jira/browse/SAMZA-1390
> Project: Samza
> Issue Type: Bug
> Reporter: Shanthoosh Venkataraman
> Assignee: Shanthoosh Venkataraman
> Priority: Minor
>
> Observed in LI production that samza-rest jvm process doesn’t stop after main
> thread death(due to jetty server failures) since non-deamon threads spawned
> for `SamzaMonitorService` are alive.
>
> * This affects samza-rest jvm process lifecycle management. To fix this,
> plugging in ThreadFactory which sets Thread name format & marks them as
> daemon.
> * Shutdown executorService in finally block (in case of any exception & also
> during normal exit).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
