Closed boposki closed 1 year ago
I don't understand.
multipathd spent more than 4 seconds to excute PARSE
what does this mean? What do you mean with PARSE, and how is it possible that it took 4 seconds? Can you fix this by simply increasing the timeout?
Btw which multipath-tools version were you using?
Procedure:
Step1: 1024 LUNs (16 paths) for an external storage are mapping to the host, then run rescan-scsi-bus.sh to produce 1024 disk. Step2: Manually issues a registration command to one of LUNs, receive timeout error. mpathpersist -o -I -S 0x000000003320095c /dev/dm-117 But if I sent a registration command with sg_persist -o -I -S 0x000000003320095c /dev/dm-117, that was successful. According the error log, I found that mpathpersist send msg of saving prkey to multipathd timeout when I config reservation_key:
Root Cause: The recv package cannot be recievd after fixed 4 seconds timeout, because multipathd spent more than 4 seconds to excute PARSE, which triggers vector lock collision with checkerloop.
Solution Suggestion: Modify client timeout to uxsock_timeout value rather than DEFAULT_REPLY_TIMEOUT , that will be consistent with server, and that would make more sense: Client wait timeout should be more than Server excecution Timeout,
considering the transmission delay. After that, uxsock_timeout in /etc/multipath.conf can be modified to more than default value such as 10 seconds.