[jira] [Updated] (SENTRY-893) Synchronize calls in SentryClient and create sentry client once per request.

["Sravya Tirukkovalur (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SENTRY-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sravya Tirukkovalur updated SENTRY-893:
---------------------------------------
    Summary: Synchronize calls in SentryClient and create sentry client once per request.  (was: Synchronize calls in SentryClient)

> Synchronize calls in SentryClient and create sentry client once per request.
> ----------------------------------------------------------------------------
>
>                 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/%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)