[jboss-jira] [JBoss JIRA] (WFWIP-266) no way how to force scale down

Martin Svehla (Jira) issues at jboss.org
Thu Nov 14 09:52:00 EST 2019


Martin Svehla created WFWIP-266:
-----------------------------------

             Summary: no way how to force scale down
                 Key: WFWIP-266
                 URL: https://issues.jboss.org/browse/WFWIP-266
             Project: WildFly WIP
          Issue Type: Bug
          Components: OpenShift
            Reporter: Martin Svehla
            Assignee: Ondrej Chaloupka


inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it

{quote}
When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered.

There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state.
{quote}

There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down. 

Users might want it during development, where data integrity doesn't matter. 





--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list