Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.3.0
-
None
-
None
Description
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
And we should add a test to make sure scans are not bringing down the Sentry service.
Example test:
curl http://$(hostname -f):8038
Attachments
Attachments
Issue Links
- is related to
-
SENTRY-909 Make max message size in ThriftSerializer configurable
- Open
-
SENTRY-910 Ideal max message size
- Open
- links to