You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2016/11/23 21:11:58 UTC

[jira] [Issue Comment Deleted] (SENTRY-1526) Sentry processed stays alive after being killed

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

Alexander Kolbasov updated SENTRY-1526:
---------------------------------------
    Comment: was deleted

(was: Here is a list of Java threads after sentry process got a signal:

{code}
Group system:
  (java.lang.ref.Reference$ReferenceHandler)0x12       Reference Handler                         cond. waiting
  (java.lang.ref.Finalizer$FinalizerThread)0x11        Finalizer                                 cond. waiting
  (java.lang.Thread)0x10                               Signal Dispatcher                         running
Group main:
  (java.lang.Thread)0x13                               main                                      cond. waiting
Group org.apache.sentry.SentryMain:
  (java.lang.Thread)0xf                                org.apache.sentry.SentryMain.main()       cond. waiting
  (java.lang.Thread)0xe                                SentryService-0                           running
  (com.mysql.jdbc.AbandonedConnectionCleanupThread)0xd Abandoned connection cleanup thread       cond. waiting
  (com.google.common.base.internal.Finalizer)0xc       com.google.common.base.internal.Finalizer cond. waiting
  (java.lang.Thread)0xb                                BoneCP-keep-alive-scheduler               cond. waiting
  (java.lang.Thread)0xa                                BoneCP-pool-watch-thread                  cond. waiting
  (com.google.common.base.internal.Finalizer)0x9       com.google.common.base.internal.Finalizer cond. waiting
  (java.lang.Thread)0x8                                BoneCP-keep-alive-scheduler               cond. waiting
  (java.lang.Thread)0x7                                BoneCP-pool-watch-thread                  cond. waiting
  (java.lang.Thread)0x6                                metrics-console-reporter-thread-1         cond. waiting
  (com.google.common.base.internal.Finalizer)0x5       com.google.common.base.internal.Finalizer cond. waiting
  (java.lang.Thread)0x4                                BoneCP-keep-alive-scheduler               cond. waiting
  (java.lang.Thread)0x3                                BoneCP-pool-watch-thread                  cond. waiting
  (com.google.common.base.internal.Finalizer)0x2       com.google.common.base.internal.Finalizer cond. waiting
  (java.lang.Thread)0x1                                BoneCP-keep-alive-scheduler               cond. waiting
  (java.lang.Thread)0x0                                BoneCP-pool-watch-thread                  cond. waiting
{code}
)

> Sentry processed stays alive after being killed
> -----------------------------------------------
>
>                 Key: SENTRY-1526
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1526
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 1.8.0, sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>
> When a running Sentry daemon receives SIGINT it doesn't terminate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)