与API私有SnapMirror相比、针对API SnapMirror的REST修补程序速度较慢
适用场景
- ONTAP 9 REST API
- SnapMirror通过修补程序/API/snapmirror/暂停或恢复
问题描述
- SnapMirror关系使用REST暂停
PATCH /api/snapmirror/relationships。 X-Trace-Threshold: 0在API调用中添加了额外的标头、以便ONTAP 为API执行提供一个跟踪：
curl -u <username> -ik -H 'X-Trace-Threshold: 0' -X PATCH "https://<cluster_mgmt>/api/snapmirror/relationships/abcdef12-3456-7890-abcd-ef1234567890?failover=false&force-failover=false&force=false&failback=false&return_timeout=120" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"state\": \"quiesced\"}"
-
TRACE RESULTS输出TOTAL将在Time(s)列下以秒为单位引用总运行时间、在此示例28.007054中为秒：
TOTAL 28.007054 4560520 3313496 1250047272 1245486752 7488813
- 在所有SnapMirror关系中迭代为
quiesce或resume、显示了总运行时间的严重波动：
TOTAL 2.243367 108536 1555280 135777912 135669376 748900
TOTAL 6.317346 812448 1316560 380904776 380092328 2225330
TOTAL 5.647037 640168 1085064 337228984 336588816 1962052
TOTAL 20.066069 256184 2077816 1149995480 1149739296 6877598
TOTAL 13.994593 271024 1246936 786166392 785895368 4685152
TOTAL 15.047924 -214920 2056520 873587096 873802016 5227347
TOTAL 10.544924 -364760 2231864 609750584 610115344 3651247
TOTAL 0.949309 618784 1059000 65859976 65241192 337164
TOTAL 0.928465 607896 1057768 65932456 65324560 331695- 在最糟糕的情况下、如果REST响应超过、
return_timeout则REST调用将返回HTTP 502错误。 - 同时
PATCH、针对其他API的速度/api/clusterlocation也非常快、例如、用于更新注释字段：
curl -u <username> -ik -H 'X-Trace-Threshold: 0' -X PATCH "https://<cluster>/api/cluster?return_timeout=120" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"location\": \"just a test to compare against snapmirror PATCH\"}"
...
TOTAL 0.005913 64296 86616 213960 149664 1005
...- 此外、针对的CLI或REST API
PATCH/private/cli/snapmirror速度也会不断加快：
::*> snapmirror resume {-status quiesced -destination-path *} -smftrace
...
----------------------------------------------------------------------------------
TOTAL 0.046835 -11936 972408 5757776 5769712 21116...