[jira] [Commented] (SENTRY-893) Synchronize calls in SentryClient

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on SENTRY-893:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12761664/SENTRY-893.patch against master.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/864/console

This message is automatically generated.

> 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.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/%3CA0F963DCF29346458CDF2969683DF6CC70F90B3A@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)