[
https://issues.apache.org/jira/browse/SENTRY-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906517#comment-14906517
]
Sravya Tirukkovalur commented on SENTRY-893:
--------------------------------------------
Hitting a weird issue where auth is called multiple times when doing "drop
table" and seems like it is not closing one of the client connections well.
> Synchronize calls in SentryClient
> ---------------------------------
>
> Key: SENTRY-893
> URL: https://issues.apache.org/jira/browse/SENTRY-893
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Sravya Tirukkovalur
> Assignee: Sravya Tirukkovalur
> Fix For: 1.7.0
>
> Attachments: SENTRY-893.1.patch, SENTRY-893.patch
>
>
> We periodically see "out of sequence response" error from thrift layer as
> thrift itself is not thread safe and lets mutliple clients read each other's
> sockets. See
> http://mail-archives.apache.org/mod_mbox/thrift-user/201208.mbox/%3ca0f963dcf29346458cdf2969683df6cc70f90...@sc-mbx01-2.thefacebook.com%3E
> bq. Caused by: sentry.org.apache.thrift.TApplicationException:
> list_sentry_privileges_for_provider failed: out of sequence response at
> sentry.org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:76)
> Would be best to synchronize the calls on client side to avoid this
> situation. We might follow up to allow locking just the transport.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
