How to correct deployed JAR files version inconsistencies manually
Article ID: 294433
Updated On:
Products
VMware Tanzu Gemfire
Issue/Introduction
You may be in a situation where there are some inconsistent JAR file versions in the output of the gfsh command list deployed.
This can result in the failure to un-deploy existing JAR:
This can result in the failure to un-deploy existing JAR:
gfsh> list deployed
Member | Deployed JAR | JAR Location
--------- | -------------------- | -------------------------------------------------
datanode1 | functionX.jar | /usr/local/gemfire/deploy/functionX.v1.jar
datanode1 | functionY.jar | /usr/local/gemfire/deploy/functionY.v1.jar
datanode2 | functionX.jar | /usr/local/gemfire/deploy/functionX.v1.jar
datanode2 | functionY.jar | /usr/local/gemfire/deploy/functionY.v1.jar
datanode3 | functionX.jar | /usr/local/gemfire/deploy/functionX.v2.jar
datanode3 | functionY.jar | /usr/local/gemfire/deploy/functionY.v1.jar
Environment
Product Version: Other
Resolution
This inconsistency of JAR file versions can be caused by stuck threads from a function execution service or a failure to remove some deployed JAR files under the deployment working directory.
You can follow the below steps to correct deployed JAR files versions inconsistencies manually:
1. Shutdown the whole cluster including locators and cacheservers.
2. Confirm the deploy working directory path from "deploy-working-dir" property in the locator's log file or the cacehserver's log file.
For example:
Note: Locator's versioning JAR files locate in "[deploy-working-dir]/cluster_config/cluster" directory when this cluster enables Cluster configuration service.
3. Confirm in the deployment working directory and decide a latest version copy of JAR files.
For example, from the above list deployed output, we can see that datanode3 have latest copy of all JAR files.
4. Remove all existing JAR file versions from all nodes except the node which has the latest copy and copy the latest copy of JAR files to all locators and cacheservers.
5. Restart the whole cluster including locators and cacheservers.
You can follow the below steps to correct deployed JAR files versions inconsistencies manually:
1. Shutdown the whole cluster including locators and cacheservers.
2. Confirm the deploy working directory path from "deploy-working-dir" property in the locator's log file or the cacehserver's log file.
For example:
deploy-working-dir=/var/vcap/store/gemfire-server
Note: Locator's versioning JAR files locate in "[deploy-working-dir]/cluster_config/cluster" directory when this cluster enables Cluster configuration service.
3. Confirm in the deployment working directory and decide a latest version copy of JAR files.
For example, from the above list deployed output, we can see that datanode3 have latest copy of all JAR files.
4. Remove all existing JAR file versions from all nodes except the node which has the latest copy and copy the latest copy of JAR files to all locators and cacheservers.
5. Restart the whole cluster including locators and cacheservers.
Feedback
Yes
No
Powered by
