Admin
From Resin 3.0
| (3 intermediate revisions by one user not shown) | |||
| Line 5: | Line 5: | ||
Administration Topics: | Administration Topics: | ||
| − | |||
; [[Admin: Load Balance]] | ; [[Admin: Load Balance]] | ||
| − | |||
; [[Admin: Ports]] | ; [[Admin: Ports]] | ||
; [[Admin: Postmortem]] | ; [[Admin: Postmortem]] | ||
; [[Admin: Profile]] | ; [[Admin: Profile]] | ||
| − | |||
| − | |||
= [[Admin: Heartbeat| Cluster Heartbeat]] = | = [[Admin: Heartbeat| Cluster Heartbeat]] = | ||
| Line 18: | Line 14: | ||
Resin's cluster checks its connectivity to the [[triad]] every minute, quickly detecting and reporting any connectivity or server problems. | Resin's cluster checks its connectivity to the [[triad]] every minute, quickly detecting and reporting any connectivity or server problems. | ||
| − | [[Image:Heartbeat-c-down.png| | + | [[Image:Heartbeat-c-down.png|center|Heartbeat Admin]] |
| Line 25: | Line 21: | ||
Resin's health check system performs a self-test every five minutes to verify that Resin is running properly. In severe cases, like out of memory conditions or deadlocks, the health check can restart Resin, keeping your server running while you debug any underlying problems. | Resin's health check system performs a self-test every five minutes to verify that Resin is running properly. In severe cases, like out of memory conditions or deadlocks, the health check can restart Resin, keeping your server running while you debug any underlying problems. | ||
| − | [[Image:Health Check.png|Health Check]] | + | [[Image:Health Check.png|center|Health Check]] |
= [[Admin: Graphs|Graphs and Meters]] = | = [[Admin: Graphs|Graphs and Meters]] = | ||
| Line 31: | Line 27: | ||
The graph and meter service lets you dynamically examine the history of data gathered by Resin's sensor and meter system across the cluster. | The graph and meter service lets you dynamically examine the history of data gathered by Resin's sensor and meter system across the cluster. | ||
| − | [[Image: Graphs-threads.png]] | + | [[Image: Graphs-threads.png|center]] |
= [[Admin: Memory|Memory]] = | = [[Admin: Memory|Memory]] = | ||
| Line 37: | Line 33: | ||
You can use the /resin-admin [[Admin: Memory|memory]] graphs for capacity planning or for postmortem analysis. If the memory usage varies considerably, you might be spending more time in garbage collection than necessary. If the memory is consistently low, or is low for an extended period of time, you might have a memory leak. The graphs will give you a starting point to determine what's happening in your system. | You can use the /resin-admin [[Admin: Memory|memory]] graphs for capacity planning or for postmortem analysis. If the memory usage varies considerably, you might be spending more time in garbage collection than necessary. If the memory is consistently low, or is low for an extended period of time, you might have a memory leak. The graphs will give you a starting point to determine what's happening in your system. | ||
| − | [[Image: Memory-free.png]] | + | [[Image: Memory-free.png|center]] |
= [[Admin: Thread Dump|Thread Dumps]] = | = [[Admin: Thread Dump|Thread Dumps]] = | ||
| Line 43: | Line 39: | ||
To debug a server that's slow or stuck, you can use the thread dump page to see exactly what the JVM is doing at a point in time. | To debug a server that's slow or stuck, you can use the thread dump page to see exactly what the JVM is doing at a point in time. | ||
| − | [[Image:Thread-dump-locking.png]] | + | [[Image:Thread-dump-locking.png|center]] |
= [[Admin: WebApp|WebApp]] = | = [[Admin: WebApp|WebApp]] = | ||
| Line 50: | Line 46: | ||
| − | [[Image:Webapps-overview.png]] | + | [[Image:Webapps-overview.png|center]] |
The deployment view of the webapp will show the deployment version for all servers in the cluster at once. | The deployment view of the webapp will show the deployment version for all servers in the cluster at once. | ||
| − | [[Image:Webapp-deploy.png]] | + | [[Image:Webapp-deploy.png|center]] |
Latest revision as of 01:22, 15 October 2010
Contents |
Topic List
Administration Topics:
Cluster Heartbeat
Resin's cluster checks its connectivity to the triad every minute, quickly detecting and reporting any connectivity or server problems.
Health Check Monitoring
Resin's health check system performs a self-test every five minutes to verify that Resin is running properly. In severe cases, like out of memory conditions or deadlocks, the health check can restart Resin, keeping your server running while you debug any underlying problems.
Graphs and Meters
The graph and meter service lets you dynamically examine the history of data gathered by Resin's sensor and meter system across the cluster.
Memory
You can use the /resin-admin memory graphs for capacity planning or for postmortem analysis. If the memory usage varies considerably, you might be spending more time in garbage collection than necessary. If the memory is consistently low, or is low for an extended period of time, you might have a memory leak. The graphs will give you a starting point to determine what's happening in your system.
Thread Dumps
To debug a server that's slow or stuck, you can use the thread dump page to see exactly what the JVM is doing at a point in time.
WebApp
The /resin-admin WebApp page gives an overview of all your deployed web-apps, and version deployment across the cluster. You can quickly check on the health of a WebApp and verify that all servers in your cluster are running the same version of the webapp.
The deployment view of the webapp will show the deployment version for all servers in the cluster at once.
