1. glassfish
  2. GLASSFISH-14859

start-cluster needs way to override number of instances started concurrently


    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1_ms06
    • Fix Version/s: future release
    • Component/s: admin
    • Labels:


      Right now when start-cluster is run it determines how many instances to start in parallel by taking the admin threadpool number and dividing it in half. So if the admin thread pool max size is 50 it will start up to 25 instances concurrently. This works great if the instances are spread across a number of machines, but if all the instances are on the same machine, or worse local to the DAS, then this can be inefficient.

      A couple ways to address this:

      • Add an option to start-cluster to indicate how many instances to start in parallel (--parallel #)
      • Add a property or environment variable to indicate how many instances to start in parallel.
      • Make the algorithm in start-instance smarter so that it limits the number of simultaneous instances started on any given node.

      I'm thinking the first option probably makes the most sense.


        Joe Di Pol created issue -
        Joe Di Pol made changes -
        Field Original Value New Value
        Fix Version/s 3.2 [ 10969 ]
        Jill Sato made changes -
        Fix Version/s 4.0 [ 10970 ]
        Fix Version/s 3.2 [ 10969 ]
        Joe Di Pol made changes -
        Fix Version/s future release [ 11148 ]
        Fix Version/s 4.0 [ 10970 ]


          • Assignee:
            Joe Di Pol
            Joe Di Pol
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: