You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Thomas Watson (JIRA)" <ji...@apache.org> on 2016/09/08 20:56:20 UTC

[jira] [Created] (ARIES-1609) Increase timeout for subsystem locking strategy and make it configurable

Thomas Watson created ARIES-1609:
------------------------------------

             Summary: Increase timeout for subsystem locking strategy and make it configurable
                 Key: ARIES-1609
                 URL: https://issues.apache.org/jira/browse/ARIES-1609
             Project: Aries
          Issue Type: Bug
            Reporter: Thomas Watson


With a large number of large subsystems the contention for the locks managed by LockingStrategy class in subsystems may be very high.  The current timeout is hardcoded to 30 seconds.  In scenarios that use provision dependencies at start (instead of at install) this contention may increase if a large number of subsystems are staged and are in the state waiting to provision dependencies.  Once the first subsystem is started it may result in a very large number of the currently installed subsystems to all provision dependencies at once.  This can take over 30 seconds.  If multiple threads are attempting to start the subsystems at the same time this may cause the timeout for the losing threads.

I think the default timeout should be increased to something pretty large.  I suggest 10 minutes.  And we should likely allow a property to override the default timeout.



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