Hi All,

We are running with an Active/ Passive terracotta cluster. Node 1 Active and Node 2 is passive. I could see the terracotta wrapper log say every time we startup on the Node 1.

Started and Becoming the activities coordinator and the Terracotta server is started and is now ready for work.

We could see the below sequence of the log.

1. The terracotta server is started and is now ready for work.
2. Node 2 joined the cluster
3. Requesting Node to Quit
4. Error Type: Newly joined Node Contains dirty Database
5. Node 2 left the cluster
6. Node 2 joined the cluster

As of now, we have not faced any issue with missing cache or API Gateway server which is using terracotta for cluster also not having any issue.

We wanted to get rid of this message from your running instance. As it would create the support team to validate the logs for every time we restart the server. I was going over the post about the dirty DB.

I would like wanted to make sure we are not deleting any data as part of the dirty clean. Also Is there any other way could solve this problem ?

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/312861c6b465633472975732f29aa8e685160962.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/312861c6b465633472975732f29aa8e685160962.jpeg 2x" data-dominant-color="2B302D">

Terracotta_server_wrapper756×320 82 KB

Hi Dinesh,

To restart the cluster, first start the server that was last active. If clustered data is not persisted, any of the servers could be started first as no data conflicts can take place.

or

You need to clean/delete dirty objects in on node2 which are persisting after re-start of node and do a clean re-start of TC.