Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.5.0
-
None
Description
We're using scribe source, some hacker like infosec guys send some malicious frames to flume with the frame size field set to a very big integer, then the thrift server inside scribe source will exit due to OOM. Then scribe source will keep wait_close state and can not accept any connection.
Attachments
Attachments
Issue Links
- is duplicated by
-
FLUME-2405 Flume stops working on arbitrary Frame Size more than 16 MB on ScribeSource
- Resolved
- relates to
-
FLUME-2984 Default maxReadBufferBytes might cause OOM and cause thrift source exit
- Patch Available