Pod Draining Not Working with template based installation of AMQ 7.5 on OpenShift.

Solution Verified - Updated -

Issue

  • I have two persistence clustered AMQ brokers in a project on OpenShift Container Platform, let's say the names are broker0 and broker1, which were created using Template (not Operator). Pod draining doesn't work when one out of two brokers is scaled down, in this case broker1 will be down after the scale down process. I expect the pod draining works so messages in the broker that is down can be migrated to another one that is still up. Is there another way to simulate the pod draining process other than scaling down the pod?

Environment

  • Red Hat AMQ
    • 7.5.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content