Vertica database hang up issue error SP_receive: Connection closed by spread-CodePudding

Vertica. Above the log log found the following error message
The error SP_receive: Connection closed by spread
.
The error SP_receive: The network socket experienced an error. This Spread mailbox will no longer work until The connection is disconnected and then reconnected
Stop: disconnecting # # node_a N015041009057 from daemon, spread Mbox=13
...
VSpread disconnected: lost connection to the daemon/opt/vertica/spread/TMP/4803
...
[Shutdown] Shutting down this node
...

Check the vertica. Other log log information
The COPY or storage table query system in the vertica. The log log often report similar to the following information
Sortmanager found maxmerges 7 too small (0 MB assigned)
After disabling optimization, maxmerges become 15
.
Sortmanager found maxmerges 2 too small (64 MB assigned)
After disabling optimization, maxmerges become 15
.
Personal understanding, the copy ROS storage file will be sorted, it comes to sort sort query system table will have this information, I try to adjust the resource pool configuration increase syaquery and sysdata allocation of resources, but the information is still exist, but don't know if this information is the cause of spread process hang up, don't know why the background spread process may hang up
Hope everybody vertica great god gives give directions, thank you very much,

CodePudding user response:

Problem solved, please? I also encountered this problem,,