As mentioned in ignite documentation, I am starting the ignite webconsole and web agent using the below scripts. We have 3 ignite clusters to monitor (3 web agents):
./gridgain-web-console-linux --server:port 3000
./ignite-web-agent.sh
What is the script to gracefully shutdown the ignite webconsole and webagent components.
At present, I am manually killing the respective process ids.
Need to schedule the startup and shutdown of ignite webconsole on the server.
If Web Console is started from console, you can just press Ctrl-C to terminate it.
If it is detached or needed to be killed automatically, you can use kill <pid>.
Related
I have a weblogic cluster with cluster node running in 2 VMs to have resiliency during failure in any node. I use the WLST scripts to manage the start & stop of the deployed components as some components will be brought down during specific time frame.
Incase VM in which admin console is running is down, Is there any way to start / stop my deployed components if Im not able to bring up the admin console.
I am running a Airflow (v2.3.3) cluster on on-premise virtual machines and starting the Airflow scheduler, webserver, and workers through SSH. However, after some time of leaving the SSH session, the Airflow scheduler unexpectedly shut down. I have two following questions:
Why does an Airflow scheduler shut down?
How do I make sure that Airflow processes (including the scheduler) are running despite leaving the SSH session?
we have ambari cluster with 872 data-nodes machines , when ambari version is 2.6.x
we have for now some network problem ,
after long investigation we found that , ambari agent that runs on some machine not communicate well with the ambari server
therefore we get some strange behaviors as 5 dead data-nodes from ambari dashboard , while for sure datanodes machine are healthy
is it possible to give more tolerated value in ambari agent configuration so the ack between ambari agent to ambari server will be after more little time in order to ignore the network problems ?
something like timeout or time connection between the ambari agent to ambari server
First of all, you need to get the root cause of the issue why Data Node is showing as Dead.
Ambari agent runs on every node. It is responsible for sending
metrics and heartbeat to the Ambari server which then publishes to
your Ambari web UI.
The name node waits for 10 minutes till it declares the data node as dead and copies
the blocks to other data nodes.
If it's showing that data node is dead then please check the Ambari agent status in
the specific node by running-service ambari-agent status. Parallelly you can check the ambari-agent.log in the worker node to check why Ambari agent stopped working.
You can configure your http timeouts in ambari-agents for service tasks, http timeouts
https://github.com/apache/ambari/blob/trunk/ambari-agent/conf/unix/ambari-agent.ini
There's a HTTP Timeout section you can configure it based on your network throughput.
The file should be in /etc/ambari-agent/ambari.properties
I want to write script for restarting weblogics managed servers, which would do the following:
It would contain loop ,which would restart first nodes of all clusters at one time.
a.)FORCE_SHUTDOWN
b.)wait for status: SHUTDOWN
c.)START managed servers
d.)wait for status: RUNNING
e.)move to next node of each cluster and repeat until all managed servers are restarted.
So in first iteration it would restart all first nodes of each cluster, in second iteration it would restart the second nodes of each cluster and repeat this action until all managed servers are restarted.
I have not started to writing the script yet, I am newbie with weblogic and this is just concept. Do you have any suggestions how to achieve that goal?
Why reinvent the wheel?
rollingRestart
Category: Control Commands
Use with WLST: Online
Description Initiates a rolling restart of all servers in a domain or all servers in a specific cluster or clusters without interrupting
the service. This command provides the ability to sequentially restart
servers.
This operation involves the graceful shutdown of the servers, and the
servers being restarted without interrupting the service for the user.
Syntax
rollingRestart(target, [options])
I have Redis server running on CentOS as a service. I can stop the server using service redis stop or redis-cli SHUTDOWN.
What is the difference between the two options and which one I should be using in Production environment?
You should check your init script since it may precisely perform a shutdown on stop and not a killproc, e.g:
ExecStop=/usr/bin/redis-cli shutdown
(from Fedora package: redis-server.service)
Using shutdown is the recommended way to stop Redis if persistence matters as stated by the documentation:
If persistence is enabled this commands makes sure that Redis is switched off without the lost of any data.