Skip to content

Conversation

linzebing
Copy link
Member

@linzebing linzebing commented Jun 7, 2023

Description

Now we create all tasks upfront and we schedule them immediately. This PR changes to only schedule a task when it has actually received non-replicated splits

Additional context and related issues

#17596

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Jun 7, 2023
@linzebing linzebing force-pushed the schedule-when-received-split branch from 795423d to 6c954bd Compare June 7, 2023 14:55
@linzebing linzebing requested a review from arhimondr June 7, 2023 18:39
@linzebing linzebing changed the title Only schedule FTE task when it receives splits Only schedule FTE task when it receives partitioned splits Jun 7, 2023
@linzebing linzebing force-pushed the schedule-when-received-split branch from 8102efe to 5251d10 Compare June 7, 2023 18:48
@linzebing linzebing force-pushed the schedule-when-received-split branch from 5251d10 to 7621870 Compare June 7, 2023 19:46
@linzebing linzebing changed the title Only schedule FTE task when it receives partitioned splits Don't schedule FTE task if it only received replicated splits Jun 7, 2023
@linzebing linzebing changed the title Don't schedule FTE task if it only received replicated splits Only schedule FTE task if it only received non-replicated splits Jun 7, 2023
@linzebing linzebing changed the title Only schedule FTE task if it only received non-replicated splits Only schedule FTE task if it received non-replicated splits Jun 7, 2023
@linzebing linzebing force-pushed the schedule-when-received-split branch 2 times, most recently from 16ed103 to e7db557 Compare June 7, 2023 20:33
@linzebing linzebing requested a review from arhimondr June 7, 2023 20:35
@linzebing linzebing force-pushed the schedule-when-received-split branch from e7db557 to 8b3fdfc Compare June 8, 2023 03:25
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a great name; at this point task is not scheduled, just merly put in the scheduling queue for scheduling late. Let's keep for now as it at least is in-line with PrioritizedScheduledTask

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was using taskCreated, but @arhimondr suggested to change to taskScheduled:)

Copy link
Member

@losipiuk losipiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM % comments.

I am not a big fan of readyForScheduling field name. It can flip flop true/false/true/false - and name suggest that when it becomes false the partition is no longer ready for scheduling - which is not true.

No good idea for rename though :P

Copy link
Member

@losipiuk losipiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM % comments.

I am not a big fan of readyForScheduling field name. It can flip flop true/false/true/false - and name suggest that when it becomes false the partition is no longer ready for scheduling - which is not true.

No good idea for rename though :P

Copy link
Member

@losipiuk losipiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM % comments.

I am not a big fan of readyForScheduling field name. It can flip flop true/false/true/false - and name suggest that when it becomes false the partition is no longer ready for scheduling - which is not true.

No good idea for rename though :P

@linzebing linzebing force-pushed the schedule-when-received-split branch from 8b3fdfc to 4a518f0 Compare June 8, 2023 16:58
@linzebing linzebing requested a review from losipiuk June 8, 2023 16:58
@arhimondr arhimondr merged commit cd4bb2b into trinodb:master Jun 8, 2023
@github-actions github-actions bot added this to the 420 milestone Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants