🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Solace Process level information and internal architecture
Hi,
I would like to understand more about the internal services that ensemble Solace PubSub s/w. I found that below processes are running as child processes of SolaceDaemon process:
1000001 24106 24081 0 Feb29 pts/0 00:00:00 /usr/sw/loads/soltr_9.3.1.9/bin/solacedaemon --vmr -z -f /usr/sw/loads/soltr_9.3.1.9/SolaceStartup.txt -r -1 1000001 24602 24106 0 Feb29 pts/0 00:42:40 python /usr/sw/loads/soltr_9.3.1.9/scripts/vmr-solaudit -d 1000001 24613 24106 0 Feb29 pts/0 00:00:07 /sbin/rsyslogd -n 1000001 24653 24106 0 Feb29 pts/0 00:00:33 /usr/sw/loads/soltr_9.3.1.9/bin/watchdog -w 0 -R 900 1000001 24654 24106 17 Feb29 pts/0 16:11:38 /usr/sw/loads/soltr_9.3.1.9/bin/dataplane -h 80 1000001 24655 24106 0 Feb29 pts/0 00:06:29 /usr/sw/loads/soltr_9.3.1.9/bin/controlplane -h 80 1000001 24656 24106 0 Feb29 pts/0 00:00:14 /usr/sw/loads/soltr_9.3.1.9/bin/smrp 1000001 24657 24106 0 Feb29 pts/0 00:09:27 /usr/sw/loads/soltr_9.3.1.9/bin/mgmtplane 1000001 24658 24106 0 Feb29 pts/0 00:00:14 /usr/sw/loads/soltr_9.3.1.9/bin/xmlmanager 1000001 24659 24106 0 Feb29 pts/0 00:00:15 /usr/sw/loads/soltr_9.3.1.9/bin/trmmanager 1000001 24660 24106 0 Feb29 pts/0 00:01:57 /usr/sw/loads/soltr_9.3.1.9/bin/msgbusadapter 1000001 24661 24106 0 Feb29 pts/0 00:00:26 /usr/sw/loads/soltr_9.3.1.9/bin/solcachemgr 1000001 24795 24106 10 Feb29 pts/0 09:28:49 /usr/sw/loads/soltr_9.3.1.9/firmware/3206/dataplane-linux 1000001 24866 24106 0 Feb29 pts/0 00:00:08 uwsgi --ini loads/soltr_9.3.1.9/scripts/sempv2/uwsgi.ini --set sempV1Port=1025 1000001 24867 24106 0 Feb29 pts/0 00:00:00 nginx: master process nginx -c /usr/sw/loads/soltr_9.3.1.9/tmp/nginx.conf root 24886 24106 0 Feb29 pts/0 00:00:00 /usr/sbin/sshd -D 1000001 24895 24106 0 Feb29 pts/0 00:41:33 /usr/bin/consul agent -config-file /var/lib/solace/consul.json
I think dataplane
process is the main processes which is required to exchange messages. Consul
process is responsible for communicating with peers in the HA triplet.
Could someone help to gain more understanding about role of other listed services here? Any pointers in the documentation also would be really helpful. I am essentially trying to understand all the internal components and services in the Solace PubSub software. I tried searching in the docs but unable to find relevant detailed explanation of internal architecture.
Please help.
Thanks in advance.
Regards,
Raghu
Comments
-
solacedaemon
is the main process which contains others as child processescontrolplane
manages the redundancy. Talks to consul and watchdogdataplane
talks to peer messaging nodes on 8741 and syncs message spools. Also, has sayshello
to the peersdataplane-linux
acts as frontcontroller for messaging protocolsmgmtplane
is responsible for config-sync between peers in a ha tripletmsgbusadapter
takes care of messaging processing. Serves clientssmrp
role is to propogate subscriptions to other nodes in case of MNRsolacecachemanager
takes care of message cachingsshd
is for CLInginx
hosts UI for solAdminuwsgi
is the REST service API for SEMP v2vmr-solaudit
??trmmanager
??xmlmanager
??Could someone please validate my understanding, correct and also shed some light on role of these components?
Thanks
0