> I'm measuring a high load value on a few nodes during the update process > (which is normal), but one node keeps the high load after the process for a > long time.
I would say that either the reading that you to is overloading that one node and other traffic is getting piled up as a result, or you're stomping on page cache by reading a lot from that one node (e.g. using CL.ONE) and you're then seeing readstage backed up until the page cache or row cache is warm again. In general, unless you're running at close to full CPU capacity it sounds like you're completely disk bound, and that'll show up as a huge amount of pending ReadStage. "iostat -x -k 1" should confirm it. -- / Peter Schuller (@scode, http://worldmodscode.wordpress.com)
