The master is experiencing intermittent timeouts when connecting to the chunkserver. #564
Replies: 1 comment 5 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
My main server stopped running due to server memory issues, reporting "can't find metadata.mfs" during startup. When restarted using a backup of metadata.mfs, it was able to start successfully, and clients could mount successfully. However, after some time, I observed errors on the master server as follows:
Jan 31 16:50:59 mfsmaster-10 mfsmaster [7436]: connection with 10.0.0.1:9422 timed out
Jan 31 16:50:59 mfsmaster-10 mfsmaster[7436]: chunkserver disconnected - ip: 10.0.0.1 / port: 9422, usedspace: (1020.59 GiB), totalspace: 1003072294912 (1500.18 GiB)
Jan 31 16:51:00 mfsmaster-10 mfsmaster [7436]: connection with 10.0.0.1:9422 timed out,
and chunkserver will appear:
connection failed, error: ECONNREFUSED (Connection refused)
Jan 31 16:51:28 file-10 mfschunkserver[975]: connecting
Jan 31 16:51:28 file-10 mfschunkserver[975]: connected to Master
There are two issues:
Whether the above timeouts are caused by the timeout parameter in the configuration file or an error due to too many files?
Occasionally, the master node reports: "chunk 0000000012A232CD_00000001: there are no copies." Are there corrupt blocks, and how can they be recovered?
1、Whether the above timeouts are caused by the timeout parameter in the configuration file or an error due to too many files?
2、Occasionally, the master node reports: "chunk 0000000012A232CD_00000001: there are no copies." Are there corrupt blocks, and how can they be recovered?
Beta Was this translation helpful? Give feedback.
All reactions