[
https://issues.apache.org/jira/browse/TRAFODION-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101195#comment-16101195
]
ASF GitHub Bot commented on TRAFODION-2695:
-------------------------------------------
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 <selva.govindara...@esgyn.com>
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.
----
> SSMP process ($ZSMxxx) sees too many opens from the master process
> ------------------------------------------------------------------
>
> Key: TRAFODION-2695
> URL: https://issues.apache.org/jira/browse/TRAFODION-2695
> Project: Apache Trafodion
> Issue Type: Improvement
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> The master processes like mxosrvr or sqlci opens SSMP process to send query
> started message and query finished messages. These messages are sent to
> provide the capability to cancel the query.
> I had observed the following with mxosrvr and mxssmp interactions:
> Mxosrvr opens a connection to mxssmp
> - For get statistics command
> - Managed via ssmpManager_ in the context. This can have connections
> to all the ssmps in the cluster
> - To cancel a query
> - Managed via cbServer_ in ExCancelTcb. This connection is expected
> to go away when the cancel is passed on the mxssmp.
> - To Send query started /Query finished message
> - Managed via cbServer_ in ContextCli. If the cbServer_ is taken up
> already by the query with query started message pending, every statement
> being executed would create a connection to ssmp and managed via cbServer_ in
> ex_root_tcb of the query
> I can see many (4) opens in mxssmp dump from a mxosrvr, but I could account
> for only one connection on the mxosrvr core dump. For some other clients, I
> have seen upto 6-8 opens.
> So, I would like to change into a common connection pool for ssmps. The
> common connection pool should be managed at the contextCli.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
