Thanks Witold for your response. Yes have tried monitoring this ws pod but unlike in earlier versions I am trying to understand what are the keywords we can check to help us know the steps getting executed. Yes we have tried earlier to manually scale down and up for the server bundles but still it is time consuming. Also we have seen when we execute managestart after scaling up and down , the server bundle pods restarts multiple times and it takes approximately 45 min for server bundles with total 50+ pods to come up.
Appreciate your response .
------------------------------
Dhiraj Panjwani
------------------------------
Original Message:
Sent: Wed September 25, 2024 02:35 AM
From: Witold Wierzchowski
Subject: MAS Manage Start/Stop timings and activity
Hi Dhiraj,
when You issue managestart or managestop what actually happens is the value in ManageWorkspace CR called .spec.settings.deployment.mode is changing to up or down. This CR is observed by Manage operator, exactly by the {instance_name}-entitymgr-ws pod. You can look into logs of this pod to observe what is happening.
In case of development environments You can also disable the Manage operator and manually scale down or up the Deployment for Your ServerBundles. That is much faster approach, but remember that this will make any issues encountered in such environment not supported by IBM.
Regards,
------------------------------
Witold Wierzchowski
Solution Architect
Cohesive Poland
Original Message:
Sent: Tue September 24, 2024 02:56 AM
From: Dhiraj Panjwani
Subject: MAS Manage Start/Stop timings and activity
Hi All,
I wanted to understand if there is any way to optimize timings for the Start and Stop of Manage when we have multiple pods for clusters. Also, the other issue I see is the moment we initiate Managestart or managestop , there is no details on what is going in the logs/events/background. At least in WebSphere , the moment we stopped the cluster, we could see the JVM logs showing some activity . But in case of managestart or managestop, we need to keep waiting and check events and it takes some time ( 5 to 10 min) to actually start killing or creating pods.
Not sure if anyone see this as a problem but atleast with multiple pods for multiple clusters it takes a lot of time to start/stop.
Thanks,
Dhiraj Panjwani
------------------------------
Dhiraj Panjwani
------------------------------