GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1188

    [TRAFODION-2695] SSMP process ($ZSMxxx) sees too many opens from the …

    …master process
    
    Mxosrvr/Any master process opens a connection to mxssmp for the following:
    1) For get statistics command
       Managed via ssmpManager_ in the context. This can have connections to 
all the
       ssmps in the cluster
    
    2) To cancel a query
       Was managed via cbServer_ in ExCancelTcb. This connection was expected 
to go away
       when the cancel is passed on the mxssmp.
    
    3) To Send query started /Query finished message
       Was managed via cbServer_ in ContextCli. If this cbServer_ was taken up 
already by
       the query with query started message pending, every statement being 
executed would have
       created a connection to ssmp and managed via cbServer_ in ex_root_tcb of 
the query
    
    In an ssmp core there were many opens from a mxosrvr. To avoid many open 
connections,
    all the ssmp connections are now managed via ssmpManager_ in the default 
context.
    This connection is shared by multiple message streams by increasing the 
no-wait depth.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
ssmp_open_optimzation

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/1188.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1188
    
----
commit e311ab631be9755b1759fd6781ad90de3306f214
Author: selvaganesang <[email protected]>
Date:   2017-07-26T05:16:10Z

    [TRAFODION-2695] SSMP process ($ZSMxxx) sees too many opens from the master 
process
    
    Mxosrvr/Any master process opens a connection to mxssmp for the following:
    1) For get statistics command
       Managed via ssmpManager_ in the context. This can have connections to 
all the
       ssmps in the cluster
    
    2) To cancel a query
       Was managed via cbServer_ in ExCancelTcb. This connection was expected 
to go away
       when the cancel is passed on the mxssmp.
    
    3) To Send query started /Query finished message
       Was managed via cbServer_ in ContextCli. If this cbServer_ was taken up 
already by
       the query with query started message pending, every statement being 
executed would have
       created a connection to ssmp and managed via cbServer_ in ex_root_tcb of 
the query
    
    In an ssmp core there were many opens from a mxosrvr. To avoid many open 
connections,
    all the ssmp connections are now managed via ssmpManager_ in the default 
context.
    This connection is shared by multiple message streams by increasing the 
no-wait depth.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to