You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Lenni Kuff (JIRA)" <ji...@apache.org> on 2015/10/07 20:57:26 UTC

[jira] [Assigned] (SENTRY-904) Set max message size for thrift messages

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

Lenni Kuff reassigned SENTRY-904:
---------------------------------

    Assignee: Li Li  (was: Sravya Tirukkovalur)

> Set max message size for thrift messages
> ----------------------------------------
>
>                 Key: SENTRY-904
>                 URL: https://issues.apache.org/jira/browse/SENTRY-904
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sravya Tirukkovalur
>            Assignee: Li Li
>            Priority: Minor
>
> THRIFT-2572 can cause a service crash. Size of message can be out of range for two reasons: 1. Security scans 2. Malformatted message. 
> We can fix this by using max message size configuration provided by TBinaryProtocol like how Hive handled it [here|https://issues.apache.org/jira/browse/HIVE-8680]
> And we should add a test to make sure scans are not bringing down the Sentry service.
> Example test:
> curl http://$(hostname -f):8038



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