mq-container Readiness Probe (chkmqready) intermittently times out (when MQ Listener IS running)

We experience an intermittent issue with our readiness probe (chkmqready) on MQ pod start up. The probe fails and the pod never goes to a "ready" state. We ended up scraping its call in the sts due to production outages. Has anyone else experienced this?

Dec 11 '19 13:12 lsabados

The only issues I've ever seen are due to Kubernetes clusters which are really slow. There really isn't much code in chkmqready to go wrong (famous last words).

Dec 11 '19 14:12 arthurbarr

What do you mean by "scraping its call in the sts"?

Dec 11 '19 14:12 arthurbarr

In our environment, we found the chkmqready to be both intermittently unreliable and ineffective. We replaced (in the MQ pod sts) the execution of the chkmqready with this

      readinessProbe:
        exec:
          command:
            - chkmqready

Replaced with

    readinessProbe:
      tcpSocket:
        port: listener

Oh..and the listener value is set earlier in the sts

ports: - containerPort: 1414 name: listener

Dec 12 '19 15:12 lsabados

Oh..and the listener value is set earlier in the sts

Dec 12 '19 16:12 lsabados

Accidentally closed

Dec 12 '19 16:12 lsabados

Can someone please share the code executed by the chkmqready?

Jan 27 '21 16:01 lsabados

https://github.com/ibm-messaging/mq-container/blob/master/cmd/chkmqready/main.go

Jan 27 '21 18:01 arthurbarr