Hi,
I have several questions on ejabberd operation. Kindly please give your advice if you have any idea. Thanks in advance.
1. I have a cluster with two nodes. The database storage type of the master and slave nodes are configured by the web console. How could I do it with command line? This is important because when new node is added to the cluster, we can configure it with some scripts other than manually in web console.
2. How could I dump the configuration currently running in my cluster, such as the database storage type? I'd like get the configuration dumped as a file such that I can add it to our repo for version controlling. And, of course, could such dump be restored to ejabberd?
3. How to monitor the performance of ejabberd? I mean how much memory it is eating, how many active connections, etc. Which processes need to monitor?
4. When the business growth, when do I need to add a new node to the cluster? In other words, we need monitor the status of the servers, and need to know how to unscramble the data, which is the basis to make decision to add new machine to support our xmpp domain.
simonsun wrote: 1. I have a
1. I have a cluster with two nodes. The database storage type of the master and slave nodes are configured by the web console. How could I do it with command line? This is important because when new node is added to the cluster, we can configure it with some scripts other than manually in web console.
ejabberd itself does not provide many administrative tools for Mnesia configuration. So, you will have to enter the erlang console and use erlang commands there manually.
2. How could I dump the configuration currently running in my cluster, such as the database storage type? I'd like get the configuration dumped as a file such that I can add it to our repo for version controlling. And, of course, could such dump be restored to ejabberd?
I checked this, but it does not provide enough information:
$ ejabberdctl dump /tmp/ejab.txt
This erlang command shows more details of the Mnesia database configuration:
mnesia:info().
3. How to monitor the performance of ejabberd? I mean how much memory it is eating, how many active connections, etc. Which processes need to monitor?
Maybe that helps to start: mod_statsdx provides more ejabberd commands to get statistics, and also provides a simple WebAdmin page.
4. When the business growth, when do I need to add a new node to the cluster? In other words, we need monitor the status of the servers, and need to know how to unscramble the data, which is the basis to make decision to add new machine to support our xmpp domain.