Skip to content
  • magnus.blaudd@oracle.com's avatar
    fe1ad6e0
    Bug#19521789 NO WAY TO RESERVE SLOTS FROM USE BY NDB_CLUSTER_CONNECTION_POOL · fe1ad6e0
    magnus.blaudd@oracle.com authored
     - Add parameter --ndb-cluster-connection-pool-nodeids= which takes a comma separated list
      of nodeid(s) to use for the cluster connection pool. The parameter is readonly and
      have to be specified as command line/my.cnf option. This is in the same fashion
      as --ndb-cluster-connection-pool and a few other parameters which controls how
      connection to cluster is done.
    
     - The new parameter extends how nodeid to use for the first cluster connection
       in MySQL Server is specified:
    
     1) NDB_CONNECTSTRING=[nodeid=X,...]
    
     2) --ndb-connectstring=[nodeid=X,...]
          - will override any nodeid specified in 1)
            (actually overrides the whole connectstring)
    
     3) --ndb-nodeid=X
          - will override nodeid specified in 1) or 2)
          - this is the value passed down as "force_nodeid"
    
     4) --ndb-cluster-connection-pool-nodeids=X
          - will override nodeid specified in 1) or 2)
          - analogue to specifying --ndb-nodeid=X
          - must be same as --ndb-nodeid=X, if that argument was specified.
          - this is the new part!
    
     - The remaining nodeid(s) in the --ndb-cluster-connection-pool-nodeids list
       is used for the subsequent cluster connections.
    
     - The number of entries in the --ndb-cluster-connection-pool-nodeid list must be equal
       to the number of cluster connections in the pool, as specified
       with --ndb-cluster-connection-pool.
    fe1ad6e0
    Bug#19521789 NO WAY TO RESERVE SLOTS FROM USE BY NDB_CLUSTER_CONNECTION_POOL
    magnus.blaudd@oracle.com authored
     - Add parameter --ndb-cluster-connection-pool-nodeids= which takes a comma separated list
      of nodeid(s) to use for the cluster connection pool. The parameter is readonly and
      have to be specified as command line/my.cnf option. This is in the same fashion
      as --ndb-cluster-connection-pool and a few other parameters which controls how
      connection to cluster is done.
    
     - The new parameter extends how nodeid to use for the first cluster connection
       in MySQL Server is specified:
    
     1) NDB_CONNECTSTRING=[nodeid=X,...]
    
     2) --ndb-connectstring=[nodeid=X,...]
          - will override any nodeid specified in 1)
            (actually overrides the whole connectstring)
    
     3) --ndb-nodeid=X
          - will override nodeid specified in 1) or 2)
          - this is the value passed down as "force_nodeid"
    
     4) --ndb-cluster-connection-pool-nodeids=X
          - will override nodeid specified in 1) or 2)
          - analogue to specifying --ndb-nodeid=X
          - must be same as --ndb-nodeid=X, if that argument was specified.
          - this is the new part!
    
     - The remaining nodeid(s) in the --ndb-cluster-connection-pool-nodeids list
       is used for the subsequent cluster connections.
    
     - The number of entries in the --ndb-cluster-connection-pool-nodeid list must be equal
       to the number of cluster connections in the pool, as specified
       with --ndb-cluster-connection-pool.
Loading