Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
trunk, 3.3.2
-
None
Description
When the number of concurrent submissions on Oozie increased to 100-200 per minute, it was not able to scale and we hit Oracle issues as there were lot of CLOB columns and DB became a bottle neck.
Attachments
Attachments
Issue Links
- is related to
-
OOZIE-1413 Fail to start JPAService if DB version is not correct
- Open
- relates to
-
OOZIE-1437 paramerize size limit of setData in JsonWorkflowAction based on user's configuration
- Open