On Thu, Oct 21, 2021 at 3:56 AM Denis Polom wrote:
>
> Hi
>
> I did, problematic mon was syncing. But issue is while it's syncing,
> Ceph become unreachable. Looks like it tries to become leader but with
> not synced db which may cause Ceph inaccessible?
Can you describe more carefully what the
Hi
I did, problematic mon was syncing. But issue is while it's syncing,
Ceph become unreachable. Looks like it tries to become leader but with
not synced db which may cause Ceph inaccessible?
On 10/20/21 15:30, Michael Moyles wrote:
Have you checked sync status and progress?
A mon status
Have you checked sync status and progress?
A mon status command on the leader and problematic monitor should show if
any sync is going on. When datastores (/var/lib/ceph/mon/ by default) get
large the sync can take a long time, assuming the default sync settings,
and needs to complete before a
Do you have any backfilling operations?
In our case when backfilling was done mon joins to quorum immediately
k
Sent from my iPhone
> On 20 Oct 2021, at 08:52, Denis Polom wrote:
>
>
> Hi,
>
> I've checked it, there is not IP address collision, arp tables are OK, mtu
> also and according
Hi,
I've checked it, there is not IP address collision, arp tables are OK,
mtu also and according tcpdump there are not packet being lost.
On 10/19/21 21:36, Konstantin Shalygin wrote:
Hi,
On 19 Oct 2021, at 21:59, Denis Polom wrote:
2021-10-19 16:22:07.629 7faec9dd2700 1
also on monitor logs on monitor that is unable to join the quorum I see
following in the log file:
2021-10-19 16:22:07.629 7faec9dd2700 1 mon.ceph1@0(synchronizing) e4
handle_auth_request failed to assign global_id
2021-10-19 16:22:08.193 7faec8dd0700 1 mon.ceph1@0(synchronizing) e4
Hi Adam,
it's
ceph version 14.2.2 (4f8fa0a0024755aae7d95567c63f11d6862d55be) nautilus (stable)
19. 10. 2021 18:19:29 Adam King :
> Hi Denis,
>
> Which ceph version is your cluster running on? I know there was an issue with
> mons getting dropped from the monmap (and therefore being stuck out
Hi Denis,
Which ceph version is your cluster running on? I know there was an issue
with mons getting dropped from the monmap (and therefore being stuck out of
quorum) when their host was rebooted in Pacific version prior to 16.2.6
https://tracker.ceph.com/issues/51027. If you're on a Pacific
