My Oracle Support Banner

Non-Master nodes get stuck in LCP phase as LCP Frag Scan Watchdog not scaling over allowed time like GCP phase (Doc ID 2765163.1)

Last updated on SEPTEMBER 04, 2023

Applies to:

MySQL Cluster - Version 7.6 and later
Information in this document applies to any platform.

Symptoms

On : 7.6 version, Crashes

ACTUAL BEHAVIOR
---------------
Full Cluster Crash - error 7200: LCP fragment scan watchdog detected a problem. Please report a bug

Four nodes in an eight-node cluster shut down with the LCP error, bringing the entire cluster down. We were able to start the cluster back up but would like some help finding out what happened and how to prevent it from happening again.

Lots of warnings in the management log about LCP progress stuck on the last 1 byte:

2021-02-17 23:21:46 [MgmtSrvr] WARNING -- Node 1: LCP Frag watchdog : No progress on table 152, frag 64 for 60 s. 1 bytes remaining., state: LCP
2021-02-17 23:21:46 [MgmtSrvr] WARNING -- Node 1: LCP Frag watchdog : Checkpoint of table 152 fragment 64 too slow (no progress for > 60 s, state: LCP_WAIT_CLOSE_EMPTY
LCP Frag watchdog : Checkpoint of table 152 fragment 64 too slow (no progress for > 60 s, state: LCP_WAIT_CLOSE_EMPTY).

Working on gathering logs to upload.

EXPECTED BEHAVIOR
-----------------------
The LCP's complete and continue onward.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot rely on the stability of the NDB Cluster.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.