You can find settings for the cluster by using the address <website address >/admin/cluster. You can view CPU, memory and disk usage per cluster node and manage the cluster; see system events for all cluster nodes; make backups; perform searches in Cassandra; download JMX information and get thread dumps.
Here you can see all nodes in the SiteVision cluster. The node that you are logged in to is marked with a flag and will be referenced as the local node. Should a node be down or if you cannot access it from the local node for some other reason, it will be marked with a red X. Even if you only have one server, it will appear here.
How many copies of data are available in the cluster. Must match the number of nodes
The difference in MS between the nodes' system clocks. Should be as small as possible (use NTP on the cluster nodes) and never exceed 500 ms
How many nodes you can have in your cluster. Determined by your license
Allows you to add a new node to the cluster by opening a registration window. You must specify the node's IP address (must match the new node's listen_address). The window is open for 5 minutes.
During the registration process, the replication factor will be one higher than the number of nodes to prepare the cluster for the new node. The following must apply in order for it to be possible to add a new node;
Retrieves data from a cluster into a new stand-alone node. Like running bootstrap to a new node without being added to the cluster. After this operation, the entire database is replaced with data from backup from the seed node.
You need to specify the IP address, HTTP port (usually 80) as well as the system user and the password for the node you are to retrieve the data from, and the system user and the password for the local node where the data will be replaced.
For this function to work, the following must apply;
This function can be used to periodically retrieve data from a production cluster to a test instance. Note, however, that the function is relatively "heavy" for the node you are retrieving data from.
Note that this replaces ALL data on the local node — not just a single website. Whole database replaced.
Here it is possible to set the replication factor for the cluster. SiteVision handles the replication factor automatically and it is only in cases of error that you need to manipulate it manually. Apart from when new nodes are added to the cluster and when nodes are removed from the cluster, the replication factor should always be the same as the number of nodes in the cluster, including nodes that are down.
During an upgrade, this is interesting to get information about what is happening. What scripts are running, when they are done, how many are left. Displayed here are things that are essential when you add new nodes, shut down, lose contact, and run scripts. You also get information when you start a full indexing (may cause the node to be perceived as "slow")
Here you can switch between days.
Mirroring the most important system properties of Sitevision as well as any changes in custom/conf/sitevision.properties. It is possible to change a value by clicking on it in the list. You can also delete a value by clicking the "X on the right" when you have the mouse cursor in the list (not available for all properties). If you want to add a system property, this is done with the X at the top right.
A change of system properties usually requires a reboot to take effect.
Here are the background jobs that SiteVision runs, those that were formerly in the schedule manager. For example, search statistics, availability reports, link checks.
Here you can also add script jobs to run at certain times. You have access to SiteVision’s Public API and can create various jobs such as clearing news archives.
SiteVisionUtils is available directly in the context and should not be declared manually.
Use the pre-declared sitevisionUtils variable directly to retrieve other auxiliary classes (Utils) from the API.
Click the Add Script job button to open a new view:
The page published: 2019-03-25