[HIVE-18837] add a flag and disable some object pools in LLAP until further testing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 01/Mar/18 23:00
• Updated: 22/May/18 23:14
• Resolved: 06/Mar/18 02:16

Description

There appears to be some subtle concurrency issue in FixedSizedObjectPool that happens with multiple consumers where some object may be retrieved twice.
Unfortunately running a load test for hour(s) does not trigger it for me and overall it happens extremely rarely on non-specific tests; adding debug info at this level is a little bit difficult to determine how it could have happened and interlocked operations in the trace may actually eliminate the issue. I suspect it has something to do with aggressive assumptions made for locking and array elements and the memory model. Maybe that can be simplified without much perf loss.
Anyway, for now we will disable the pools where multiple consumers use them.
Need to test perf to see if these two pools even matter; if so, we can simplify the model as per above or debug the issue in some way.

Issue Links

• relates to: HIVE-18838 investigate potential issue in FixedSizedObjectPool and reenable it