Document scheduling policy config property#10715
Conversation
rosewms
force-pushed
the
rw-scheduling-policy
branch
from
82b149a to
32f0214
Compare
There was a problem hiding this comment.
To restore previous previous policy behavior
I think such comment makes sense only in release notes. Maybe here we should briefly enumerate all policies?
There was a problem hiding this comment.
That would be great, the info I have is based on the 368 release notes. I'd love to get some clarity on the specific policies @sopel39
rosewms
force-pushed
the
rw-scheduling-policy
branch
from
32f0214 to
4c609e8
Compare
There was a problem hiding this comment.
Maybe Phased execution schedule maximizes cluster resource utilization and provides lowest query wall time. Stages are scheduled in such a sequence that they shouldn't become blocked because of inter-stage dependency?
The previous default value ``all-at-once``, schedules all the phases of a query at one time. -> The previous default value ``all-at-once``, schedules all the stage of a query at one time.
The ``legacy-phased`` value schedules phases of a query only when it can start processing them. -> The ``legacy-phased`` schedules stages in such a sequence that they shouldn't become blocked because of inter-stage dependency. Compared to ``phased`` scheduler, ``legacy-phased`` will try to minimize number of running stages and can increase query wall time
There was a problem hiding this comment.
This was very helpful, I have a new version for review. Thanks @sopel39
rosewms
force-pushed
the
rw-scheduling-policy
branch
from
4c609e8 to
dcecdfa
Compare
There was a problem hiding this comment.
"similar" -> "has similar"
rosewms
force-pushed
the
rw-scheduling-policy
branch
from
dcecdfa to
0951d86
Compare
6 participants
#10554