Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
24.7. Cluster Administration
24.7.1. Cluster Nodes View
Copiar o linkLink copiado para a área de transferência!
Clusters centric view allows to view the nodes created for each server group and the list of deployed servers can be viewed. In Clusters view, you can add new nodes to the cluster group and view performance metrics of the particular nodes.
To access the Clusters view, navigate to the Clusters tab from the Dashboard and click on the name of the cluster.
Figure 24.72. Nodes View
24.7.2. Cluster Nodes Mismatch
Copiar o linkLink copiado para a área de transferência!
The total number of server nodes on the JBoss Data Grid cluster should ideally match the number of nodes shown in the JBoss Data Grid Administration Console. If in case, due to some reason, the expected nodes in the console do not match with the exact number of nodes on the JBoss Data Grid physical cluster, the console issues a mismatch warning by displaying the number of nodes detected and the number of expected nodes. Knowing the expected number of server nodes helps in handling Network Partitions.
If nodes mismatch occurs, it can be viewed in the clusters view, above the list of nodes as a warning. To access the Clusters view, navigate to the Clusters tab from the Dashboard and click on the name of the cluster.
In the following screen, the Console alerts the user in the form of a warning. The expected number of server nodes are 5 but only 3 are detected by the console.
Figure 24.73. Cluster Nodes Mismatch
24.7.3. Cluster Rebalancing
Copiar o linkLink copiado para a área de transferência!
The Red Hat JBoss Data Grid Administration Console allows the user to enable and disable cluster rebalancing at the cache container and cache levels.
Note
Cluster rebalancing is enabled by default.
The following procedure outlines the steps to enable and disable cluster rebalancing at a cache container level :
Procedure 24.14. Enable and Disable Rebalancing
- From the cache container view, click on the name of the cache container.
- In the caches view, at the right hand side, click on .
Figure 24.74.
- A callout menu is opened. Click .
Figure 24.75.
- A confirmation dialogue box appears. Click .
Figure 24.76.
- Cluster rebalancing is successfully disabled.
Figure 24.77.
- To enable rebalancing, click Actions > Enable Rebalancing.
Figure 24.78.
- A confirmation dialogue box appears. Click .
Figure 24.79.
Rebalancing is successfully enabled.
Figure 24.80.
The following procedure outlines the steps to enable and disable cluster rebalancing at a cache level :
Procedure 24.15. Enable and Disable Rebalancing
- From the cache container view, click on the name of the cache container.
- In the caches view, click on a specific cache.
- The cache statistics page is displayed. At the right hand side, click .
Figure 24.81.
- From the callout menu, click .
Figure 24.82.
- A confirmation dialogue box appears. Click .
Figure 24.83.
- The rebalancing for the cache is successfully disabled.
Figure 24.84.
- To enable cache level rebalancing, click from the menu.
Figure 24.85.
- A confirmation dialogue box appears. Click .
Figure 24.86.
The rebalancing for the cache is successfully enabled.
Figure 24.87.
24.7.4. Cluster Partition Handling
Copiar o linkLink copiado para a área de transferência!
The JBoss Data Grid Console alerts the user with a visual warning when the cluster changes state to DEGRADED. The assumed causes for a DEGRADED cluster are occurence of a network partition, unreachable node(s) or unexpected extra nodes.
The visual warning is displayed in the Clusters view. To access the Clusters view, navigate to the Clusters tab from the Dashboard and click on the name of the cluster. In the following screen, the visual warning DEGRADED is displayed next to the cluster name JDG Cluster #1.
Figure 24.88. Network Partition Warning
This visual warning for a DEGRADED cluster is shown at Cluster, Cache Container, and Cache levels of the console.
24.7.5. Cluster Events
Copiar o linkLink copiado para a área de transferência!
The JBoss Data Grid Console displays the cluster wide events such as cluster-split and cluster-merge events in a consolidated section. Along with the cluster events, the console displays the timestamp of the associated event. Cluster events can be viewed in the Cache containers page, the Clusters view page and also in the Status Events tab of the Dashboard.
To view cluster events on the cache containers page, navigate to the default cache containers view which is the default landing interface after logging into the console. The Cluster events is displayed at the right hand side in a consolidated section under the title Latest Grid Events
Figure 24.89.
To view the cluster events on the Clusters view page, navigate to the Clusters view by clicking on the Clusters tab. The Cluster events is displayed at the right hand side in a consolidated section under the title Latest status Events
Figure 24.90.
24.7.6. Adding Node
Copiar o linkLink copiado para a área de transferência!
The JBoss Data Grid Administration Console allows administrators to configure new nodes.
The following procedure outlines the steps to add a new Node:
Procedure 24.16. Adding a New Node
- In the Dashboard view, click tab.
Figure 24.91. Clusters Tab
- Click on the name of the cluster where the new node has to be added.
Figure 24.92. Cluster Selection
- Click .
Figure 24.93. Add Node Created
- The node configuration window is opened. Enter the node properties in the respective fields and click
Figure 24.94. Node Properties
- The system boots up.
Figure 24.95. System Boot
- The new node is successfully created.
Figure 24.96. New Node
24.7.7. Node Statistics and Properties View
Copiar o linkLink copiado para a área de transferência!
JBoss Data Grid Administration Console allows users to view the average time for reads, average times for writes, total number of entries, total number of reads, total number of failed reads, total number of writes and other data.
To view the Node statistics, click on the name of the Node in the Clusters tab on the JBoss Data Grid Administration Console.
Figure 24.97. Nodes Statistics
24.7.8. Node Performance Metrics View
Copiar o linkLink copiado para a área de transferência!
To view the Node performance metrics, click on the name of the node in the Clusters tab of the JBoss Data Grid Administration Console
Figure 24.98. Node Performance Metrics
24.7.9. Disabling a Node
Copiar o linkLink copiado para a área de transferência!
The JBoss Data Grid Administration Console allows administrators to disable nodes.
To disable a node of a cluster, follow these steps:
Procedure 24.17. Adding a New Node
- Click on the name of the cluster in the Cluster View of the JBoss Data Grid Administration Console.
- In the Nodes view, click on the node to be disabled.
Figure 24.99. Nodes View
- The Node statistics view is opened. Click on the Actions tab located at the right hand side of the page and then click .
Figure 24.100. Nodes Stop
- A confirmation box appears. Click to remove the node from the cluster.
Figure 24.101. Confirmation Box
24.7.10. Cluster Shutdown and Restart
Copiar o linkLink copiado para a área de transferência!
24.7.10.1. Cluster Shutdown
Copiar o linkLink copiado para a área de transferência!
JBoss Data Grid Administration Console allows convenient and controlled shutdown of JBoss Data Grid clusters for maintenance purposes. For caches with a configured cache store, the data will be persisted without any data loss.For caches without a configured cache store, data will be lost after cluster shutdown.
To shut down or stop a cluster, follow these steps:
Procedure 24.18. Shutting Down Cluster
- Navigate to the Clusters view in the JBoss Data Grid Administration console and click on the name of the cluster.
Figure 24.102. Clusters View
- On the Nodes view page, locate the Actions tab to the top right hand side of the interface. Click on Actions tab and then click .
Figure 24.103. Cluster Stop
- A confirmation box will appear. To confirm, click Stop.
Figure 24.104. Confirmation Box
24.7.10.2. Cluster Start
Copiar o linkLink copiado para a área de transferência!
JBoss Data Grid Administration Console allows restarting a stopped cluster. The cache data is preloaded without any data loss for caches with configured cache-store. Caches without a configured cache store, will initially contain no data.
Preloading will only happen if preload is enabled on the cache store. If the local cache state on one of the nodes is corrupt, the cache will not start and manual intervention will be required.
To a cluster, follow these steps:
Procedure 24.19. Starting Cluster
- Navigate to the Clusters view in the JBoss Data Grid Administration console and click on the name of the cluster.
- On the Nodes view page, locate the Actions tab to the top right hand side of the interface. Click on Actions tab and then click .
Figure 24.105. Cluster Start
- A confirmation box will appear. Click Start to start the cluster.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}