Use at your risk, but these were provided by VMWare support when I needed to slow down resync due to LLOG increasing nonstop:
vsish -e set /vmkModules/vsan/dom/MaxNumResyncCopyInFlight 50
50 is the default value, lowering this number will slow down resync, apply to all hosts, no reboot necessary.
I have also run into the LLOG issue increasing where LLOG could be something like 30-40gb and PLOG still at 1-2gb. This happened when upgrading my cluster from 6.0 build 4510822 to 4600944. I never got a good clear answer from support, they said not enough cache capacity but I called BS since I had every VM on my cluster powered off and no resync activity and this was still occuring, seemed like some like of LOG leak. I am running r730xds with H730s which have a problematic history, could be some problem with the raid controller too even though i'm running HCL firmware/drivers. I couldn't get support to assist me quickly enough so eventually had to destroy the affected disk group as the node took more than 12 hours to LLOG recover (causing missing objects to resync) and the affected disk group still wouldn't mount after coming back online.
Error during LLOG leaking looked something like this on the affected node:
vmkernel.log:
2016-11-27T22:57:24.924Z cpu39:44452)WARNING: VSAN: VsanSparseWriteDone:3974: Throttled: Write error on '70674b1-0c4b3858-5421-3876-4a4b-ecf4bbd4b888': token status 'IO was aborted',SCSI status 8 (OK:BUSY)
2016-11-27T22:57:26.536Z cpu7:44388)HBX: 2802: '21c03057-1a09-4711-614c-ecf4bbd4d520': HB at offset 3457024 - Waiting for timed out HB:
2016-11-27T22:57:26.536Z cpu7:44388) [HB state abcdef02 offset 3457024 gen 7 stampUS 137850214982 uuid 58390ad8-a5c516bb-6f90-ecf4bbd2f6c8 jrnl <FB 70000> drv 14.61 lockImpl 4]
2016-11-27T22:57:30.672Z cpu28:60910)LSOM: LSOM_ThrowCongestionVOB:3459: Throttled: Virtual SAN node vsan-c00-n03 maximum Memory congestion reached.
2016-11-27T22:57:41.333Z cpu1:33092)VSCSI: 2993: Retry 0 on handle 8193 still in progress after 64 seconds