Liveness probe doesn't work properly for arbiter pod

Description

In case of arbiter is enabled default liveness probe doesn't work properly.In case of arbiter is enabled default liveness probe doesn't work properly. As result arbiter pod is constantly restarting.

Trying to check a result of liveness probe:

Probably it's because of mongo shell at arbiter mongodb node can not use authentication. But mongodb-healthcheck uses authentication - https://github.com/percona/mongodb-orchestration-tools/blob/master/cmd/mongodb-healthcheck/main.go#L53.

I'm able to get rs.status() at arbiter mongodb mode without authentication:

But it doesn't work with auth parameters:

Environment

None

Smart Checklist

Activity

Sergey Pronin March 12, 2021 at 10:37 AM

Fixed in 1.7.0 release.

Done

Details

Assignee

Reporter

Fix versions

Priority

Smart Checklist

Created June 3, 2020 at 4:15 PM
Updated March 5, 2024 at 5:08 PM
Resolved March 12, 2021 at 10:37 AM