SMAX重启步骤

网友投稿 425 2022-10-27

SMAX重启步骤

重启suite

全部都在Master节点操作

查看suite namespace, 进入/opt/kubernetes/bin , 获取对应的itsma na 名称如下:

[10.225.50.90][root@cnsd2sapwill003 bin]# kubectl get nsNAME STATUS AGEcore Active 176ddefault Active 176ditsma-hdtup Active 176dkube-node-lease Active 176dkube-public Active 176dkube-system Active 176d

停止Suite

./cdfctl.sh runlevel set -l DOWN -n itsma-hdtup

执行如下命令,查看suite pods状态:watch kubectl get pods -n itsma-hdtup

This command will refresh the display of the suite pod status every two seconds.Note: All of the suite pods must be stopped 除了一下PoDS: ​​itom-nginx-ingress-deployment-xxxxx​​, and ​​itom-throttling-controller-xxxxx​​.

启动Suite

./cdfctl.sh runlevel set -l UP -n itsma-hdtup对应结果如下:NAME READY STATUS RESTARTS AGEauth-7d6bf797c4-t2k5k 2/2 Running 0 27mautopass-lm-v2-76cbc87f74-4vwgb 2/2 Running 0 27midm-78fcddccf-rzc64 2/2 Running 0 27minfra-rabbitmq-0 2/2 Running 0 26mitom-auth-deploy-controller-pod 0/1 Completed 0 175ditom-autopass-deploy-controller-pod 0/1 Completed 0 175ditom-bo-ats-deployment-6cf6fd7c76-mvndr 2/2 Running 0 27mitom-bo-config-deployment-78dd6bbf88-5cxp4 2/2 Running 0 27mitom-bo-dependency-check-pod 0/1 Completed 0 175ditom-bo-deploy-controller-pod 0/1 Completed 0 175ditom-bo-facade-deployment-74c765cd58-kb2rm 2/2 Running 0 27mitom-bo-fo-ui-deployment-97575ff98-9jhr9 2/2 Running 0 27mitom-bo-init-pod 0/1 Completed 0 175ditom-bo-license-deployment-7b98b76944-6xx7l 2/2 Running 0 27mitom-bo-login-deployment-847fd79fc6-kjj24 2/2 Running 0 27mitom-bo-ui-deployment-788c7d766b-j5wv8 2/2 Running 0 27mitom-bo-user-deployment-5d4f7c86b-4q7ns 2/2 Running 0 27mitom-bo-user-offline-deployment-788dc6f9d9-qd57r 2/2 Running 0 27mitom-idm-deploy-controller-pod 0/1 Completed 0 175ditom-ingress-deploy-controller-pod 0/1 Completed 0 175ditom-itsma-certificate-deploy-controller-pod 0/1 Completed 0 175ditom-itsma-certificate-deployment-6bfb4ff445-mvhv4 2/2 Running 0 27mitom-itsma-throttling-deploy-controller-pod 0/1 Completed 0 175ditom-nginx-ingress-deployment-6bfd794d96-ss95v 1/1 Running 0 27mitom-smartanalytics-deploy-controller-pod 0/1 Completed 0 175ditom-throttling-controller-qv74b 1/1 Running 1 175ditom-virtual-agent-deploy-controller-pod 0/1 Completed 0 175ditom-xruntime-deploy-controller-pod 0/1 Completed 0 175ditom-xruntime-gateway-7bf96fbbc-knjcw 2/2 Running 0 27mitom-xruntime-help-center-8569dfffb9-5vjfg 1/1 Running 0 27mitom-xruntime-infra-deploy-controller-pod 0/1 Completed 0 175ditom-xruntime-init-infra 0/1 Completed 0 175ditom-xruntime-lcm 0/1 Completed 1 175ditom-xruntime-mobile-gateway-77d478db76-jgddj 2/2 Running 0 27mitom-xruntime-opb-ui-84c84865f8-trzcn 1/1 Running 0 27mitom-xruntime-platform-55d5849b85-q5dl4 2/2 Running 0 27mitom-xruntime-platform-offline-645564bc8b-b76mp 2/2 Running 0 26mitom-xruntime-ppo-567c75897c-rlqxd 2/2 Running 0 26mitom-xruntime-redis-f7fc7f545-q7prg 3/3 Running 0 26mitom-xruntime-serviceportal-c9c447cd7-wxnn4 2/2 Running 0 26mitom-xruntime-ui-8666857987-2p4tq 1/1 Running 0 26mitom-xruntime-xmpp-659dd6786d-xlgpc 2/2 Running 0 26msmarta-admin-ui-backend-64f7456bc-qvb67 1/1 Running 0 26msmarta-data-source-7fc5f77f8d-pdlg2 2/2 Running 0 26msmarta-installer-5f67c4d474-pk66x 2/2 Running 0 26msmarta-ocr-548f48b4c-p4bg7 2/2 Running 0 26msmarta-saw-con-0 1/1 Running 0 26msmarta-saw-dah-0 1/1 Running 0 26msmarta-saw-dih-fd78d578-5v9rj 1/1 Running 0 26msmarta-saw-proxy-fb4c65ff8-v45zw 1/1 Running 0 26msmarta-sawarc-con-0 1/1 Running 0 26msmarta-sawarc-dah-0 1/1 Running 0 26msmarta-sawarc-dih-7bc77cb4d-r7ckp 1/1 Running 0 26msmarta-sawmeta-con-0 1/1 Running 0 26msmarta-sawmeta-dah-0 1/1 Running 0 26msmarta-sawmeta-dih-767c85d79-96mtb 1/1 Running 0 26msmarta-search-777f686d89-48sgg 2/2 Running 0 26msmarta-smart-ticket-64c4899854-k5qd4 2/2 Running 0 26msmarta-smart-ticket-admin-ui-6d99d8844b-nw95q 1/1 Running 0 26msmarta-smart-ticket-task-bf87d5fb-gjb9l 2/2 Running 0 26msmarta-stx-agent-765db5bcdc-9z5tj 1/1 Running 0 26msmarta-stx-category-bc86fc49f-98jcl 1/1 Running 0 26msmarta-stx-media-7fb74d5c6-hkrjp 1/1 Running 0 26m

重启CDF

在Master节点操作:

停止deployments, replication controller, statfulset, or cronjob相关POD

$K8S_HOME/scripts/cdfctl.sh runlevel set -l DOWN

在所有Worker节点操作:

$K8S_HOME/bin/kube-stop.sh

在所有Master节点操作:

$K8S_HOME/bin/kube-stop.sh

重启服务器(可选)

在重启服务器上,按顺序执行

systemctl restart nfssource $K8S_HOME/bin/env.sh && for m in $(df | grep "$RUNTIME_CDFDATA_HOME" | awk '{print $6}'); do umount -f -l $m; done

在所有Master节点上同时启动Kube-proxy,然后在Worker节点上启动Kube-proxy

$K8S_HOME/bin/kube-start.sh

在master节点上启动PODS

$K8S_HOME/scripts/cdfctl.sh runlevel set -l UP

检查POD状态

$K8S_HOME/bin/kube-status.sh

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:usB接口的主要特点
下一篇:升级dubbo2.7.4.1版本平滑迁移到注册中心nacos
相关文章

 发表评论

暂时没有评论,来抢沙发吧~