[ 
https://issues.apache.org/jira/browse/SENTRY-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691363#comment-15691363
 ] 

Alexander Kolbasov commented on SENTRY-1526:
--------------------------------------------

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

{code}
Group system:
  (java.lang.ref.Reference$ReferenceHandler)0x1a        Reference Handler       
                                       cond. waiting
  (java.lang.ref.Finalizer$FinalizerThread)0x19         Finalizer               
                                       cond. waiting
  (java.lang.Thread)0x18                                Signal Dispatcher       
                                       running
Group main:
  (java.lang.Thread)0x1b                                main                    
                                       cond. waiting
Group org.apache.sentry.SentryMain:
  (java.lang.Thread)0x17                                
org.apache.sentry.SentryMain.main()                            cond. waiting
  (java.lang.Thread)0x16                                SentryService-0         
                                       running
  (com.mysql.jdbc.AbandonedConnectionCleanupThread)0x15 Abandoned connection 
cleanup thread                            cond. waiting
  (com.google.common.base.internal.Finalizer)0x14       
com.google.common.base.internal.Finalizer                      cond. waiting
  (java.lang.Thread)0x13                                
BoneCP-keep-alive-scheduler                                    cond. waiting
  (java.lang.Thread)0x12                                
BoneCP-pool-watch-thread                                       cond. waiting
  (com.google.common.base.internal.Finalizer)0x11       
com.google.common.base.internal.Finalizer                      cond. waiting
  (java.lang.Thread)0x10                                
BoneCP-keep-alive-scheduler                                    cond. waiting
  (java.lang.Thread)0xf                                 
BoneCP-pool-watch-thread                                       cond. waiting
  (java.lang.Thread)0xe                                 
metrics-console-reporter-thread-1                              cond. waiting
  (com.google.common.base.internal.Finalizer)0xd        
com.google.common.base.internal.Finalizer                      cond. waiting
  (java.lang.Thread)0xc                                 
BoneCP-keep-alive-scheduler                                    cond. waiting
  (java.lang.Thread)0xb                                 
BoneCP-pool-watch-thread                                       cond. waiting
  (com.google.common.base.internal.Finalizer)0xa        
com.google.common.base.internal.Finalizer                      cond. waiting
  (java.lang.Thread)0x9                                 
BoneCP-keep-alive-scheduler                                    cond. waiting
  (java.lang.Thread)0x8                                 
BoneCP-pool-watch-thread                                       cond. waiting
  (java.lang.Thread)0x7                                 qtp990127963-28 
Selector0                                      running
  (java.lang.Thread)0x6                                 qtp990127963-29 
Selector1                                      running
  (java.lang.Thread)0x5                                 qtp990127963-30 
Acceptor0 [email protected]:51000 running
  (java.lang.Thread)0x4                                 qtp990127963-31 
Acceptor1 [email protected]:51000 waiting in a monitor
  (java.lang.Thread)0x3                                 qtp990127963-32         
                                       cond. waiting
  (java.lang.Thread)0x2                                 qtp990127963-33         
                                       cond. waiting
  (java.lang.Thread)0x1                                 qtp990127963-34         
                                       cond. waiting
  (java.lang.Thread)0x0                                 qtp990127963-35         
                                       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)

Reply via email to