[
https://issues.apache.org/jira/browse/SENTRY-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906517#comment-14906517
]
Sravya Tirukkovalur edited comment on SENTRY-893 at 9/24/15 5:22 PM:
---------------------------------------------------------------------
Previously a sentry client was being created multiple times when doing "show
tables" even when there are no tables in the db. With this patch client is not
created for "show tables" if there are no tables in the current db, hence
updating the test.
was (Author: sravya):
Auth check is now not called when doing "show tables" if there are no tables in
the current db, updating the test.
> 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.2.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)
