Select a node - properties

Clicking a node in the cluster panel displays more information. Use ESC or click next to the node to exit this information.

Serverinfo (the server’s name)

Here you will see a selection of server information such as latest backup, version, Heap, disk free, Cassandra size.

Properties

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 plus sign at the top right.

A change of system properties usually requires a reboot to take effect.

Tasks

The background jobs that SiteVisions runs. Black marked jobs are jobs that are currently running.

Logging

Here you can set logging levels for the node.

Default level

Here you see what level you are on (INFO in this example) but you can easily switch to DEBUG. This setting is saved automatically. Read more about log levels.

Change in log file

Here you can micromanage logging for specific classes or packages. This is useful if you have proprietary portlets and want to adjust the log level for specific classes or packages or for advanced troubleshooting.

If you make a change, you must click on Save config. If you entered incorrectly, you can always change your mind and return to the original file by clicking the Reset to original button.

For more information about Log4j configuration:
http://logging.apache.org/log4j/1.2/manual.html External link, opens in new window.

Indexing

Here you can see information about indexing queues. Here you will see the event queue (potential reindexing) and data queue (set reindexing).

High/low priority

Events that occur have different priority. For example, publishing a page has high priority. While a change of page name has a lower priority. If there is a long queue, all items with high priority will get go to the front. Those with low priority must wait until the queue with high priority is completed.

• Event queue - This is a queue with events that have occurred that can result in something needing to be reindexed. So even if there are 100 in the queue, only 5 may get reindexed (end up in the data queue).
• Data queue - This queue of events contains the actual reindexes to be performed.

Right-click on a node

Backup

Create a backup of existing data. The backup is made in data/backup/cassandra and is actually hard links to existing database files. Backup occurs automatically every night.

Archive backup

Creates a tar archive of the latest backup that is added in data/archive/

If you want the latest data, make a regular backup first and then archive it.

You can choose to tick the Include files box to get all binary data.

Repair

If a node has been down for longer than 6 hours, you need to run a repair on all nodes in the cluster. This is to ensure that all data is available on all nodes in the cluster.

Compact

Rewrites the database files so that it is possible to free up disk space. This is an administrative operation that you never really need to carry out. The database automatically performs compaction when needed.

Dump heap

Dumps the heap to a file. You can only do this if you have memory problems. SiteVision will not be able to take traffic while the heap is being dumped, which can take several minutes.

Dump threads

Writes a thread dump to wrapper.log that can be used to give a snapshot of what SiteVision does. Used to troubleshoot if the server is considered to be slow.

Empty instant caches

If you experience any type of unsync in the cluster, you can empty the instant caches of the node that deviates. SiteVision is then forced to reread the information from the database. Unsync should not normally occur.

Shutdown

Shuts down or restarts the node

Remove

Removes the node from the cluster. This operation requires that the node is closed