Error Message:
replay journal cost too much time: 1001 replayedJournalId: 462527012021-06-25 00:00:44,846 WARN (replayer|70) [BDBJournalCursor.next():149] Catch an exception when get next JournalEntity. key:46252706com.sleepycat.je.LockTimeoutException: (JE 7.3.7) Lock expired. Locker 1009050036 -1_replayer_ReplicaThreadLocker: waited for lock on database=46236602 LockAddr:1984482862 LSN=0x858/0x3c1ac4 type=READ grant=WAIT_NEW timeoutMillis=1000 startTime=1624550443846 endTime=1624550444846Owners: [<LockInfo locker="<ReplayTxn id="-48657952">970177120 -48657952_ReplayThread_ReplayTxn" type="WRITE"/>]Waiters: [<LockInfo locker="1009050036 -1_replayer_ReplicaThreadLocker" type="READ"/>]
There is a test service in the fe node bdb log error caused the fe hang, and then start can not start up, look at the doris-meta/bdb/under je.info.0 log found last night there is this error report
2021-06-24 16:00:47.926 UTC SEVERE [10.1.1.1_9010_1623157894289] 10.1.1.1_9010_1623157894289(4):/disk1/doris/doris-meta/bdb:DataCorruptionVerifier exited unexpectedly with exception java.io.IOException: Input/output errorjava.io.IOException: Input/output error
The inference is that there is a problem with the disk
dmesg -T | grep sda| grep error | tail -40

There is indeed a problem with the sector, you need to contact the IDC

Read More:

• [kubernetes] the pod instance of calico node always reports an error and restarts
• [Solved] Redisson distributed lock error: attempt to unlock lock, not locked by current thread by node id
• How to Solve Hmaster hangs up issue due to namenode switching in Ha mode
• Node Kubelet Error: node “xxxxx“ not found [How to Solve]
• [Solved] Clickhouse Error: DB::Exception: Cannot lock file /var/lib/clickhouse/status
• [Solved] Kafka Restarts error | Cloudera Manager Access Returns 500 | HDFS Startup Error
• [Solved] Error: unable to perform an operation on node ‘rabbit@DESKTOP-xxx‘. Please see diagnostics informa
• [Solved] Kafka2.3.0 Error: Timeout of 60000ms expired before the position for partition could be determined
• [Gradle is Stucked in Building Runing] log Error: Timeout waiting to lock journal cache
• [Solved] Rabbitmq Server Error: unable to perform an operation on node ‘rabbit@nscczzms‘. P
• failed to obtain in-memory shard lock [How to Solve]
• Docker Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid
• [Solved] k8s error retrieving resource lock default/fuseim.pri-ifs: Unauthorized
• [Solved] Rancher Add User Error: x509: certificate has expired Internal error occurred: failed calling webhook “rancherauth.cattle.io”:
• [Solved] error [email protected]: The engine “node” is incompatible with this module.
• React-native Error: Make sure you have the Android development environment set up [Solved]
• [INS-06006] Passwordless SSH connectivity not set up [Solved]
• [Solved] Git Push Error: &fatal: the remote end hung up unexpectedly
• Huawei kafka Authentication error: Server not found in Kerberos database (7) – LOOKING_UP_SERVER
• Rabbitmq failed to stop normally: ERROR: node with name “rabbit” already running on “localhost”