[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFWIP-218: --------------------------------- Comment: was deleted (was: The problem is this issue is as follows: 1. transaction log on on server is cleared correctly 2. server's stateful-set is scaled down (pod referenced by client disappears) 3. client checks in-doubt resource but cannot connect to the server In OpenShift environment with wildfly-operator, we can be sure that if the server's stateful-set was scaled down correctly then it logs must have been cleared. As a result, client records can be discarded. This is not true in general (bare-metal) where the server may go down and still have records in the log. in the context of above I would propose: 1. workaround - provide the customer with a manual procedure (if connection error to the server's pod occurs but the pod was scaled down correctly remove log records). This is not elegant, but this is an emergency and I don't expect it to be used often. 2. solution - if operating within OpenShift client cannot connect to one of the server's pods, client checks with OpenShift API whether the server's pod was scaled down. If it was, the record can be discarded. I would suggest downgrading this issue with provided workaround and later work on the target solution (which would require OpenShift integration and has to be researched).) -- This message was sent by Atlassian Jira (v7.13.8#713008)