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

Dapeng Sun commented on SENTRY-599:
-----------------------------------

We can see the output will be like:
{noformat}
TestSingleThreadExecutor-0 begin call 1
Time cost:5000
TestSingleThreadExecutor-0 end call 4
TestSingleThreadExecutor-0 begin call 4
Time cost:0
TestSingleThreadExecutor-0 end call 4
TestSingleThreadExecutor-0 begin call 4
Time cost:0
TestSingleThreadExecutor-0 end call 4
TestSingleThreadExecutor-0 begin call 4
Time cost:0
TestSingleThreadExecutor-0 end call 4
{noformat}
We expect All the "Time cost" should be 5000, but it didn't, because 
"keepRunning" had been changed by other submitted threads.

> Sentry service may report incorrect status when service is restarting
> ---------------------------------------------------------------------
>
>                 Key: SENTRY-599
>                 URL: https://issues.apache.org/jira/browse/SENTRY-599
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Dapeng Sun
>            Assignee: Dapeng Sun
>         Attachments: SENTRY-599.001.patch, SENTRY-599.002.patch, 
> SENTRY-599.003.patch, SENTRY-599.004.patch, TestSingleThreadExecutor.java
>
>
> When sentry service is restarting using same configuration and context.  
> {{server.isRunning()}} will report incorrect status.
> The root cause is {{finally}} may run after {{future = 
> serviceExecutor.submit(this);}}, the status will be {{NOT_STARTED}} even the 
> thrift server is started



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

Reply via email to