Skip to content

fix: handle None task slot in update_task_info after executor lost #1523

Open
milenkovicm wants to merge 1 commit intoapache:mainfrom
milenkovicm:spiceai_23
Open

fix: handle None task slot in update_task_info after executor lost #1523
milenkovicm wants to merge 1 commit intoapache:mainfrom
milenkovicm:spiceai_23

Conversation

@milenkovicm
Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Closes #.

Rationale for this change

When an executor heartbeat times out, reset_tasks() sets task_infos[partition_id] to None. If the executor later reconnects and sends a late status update, update_task_info() would panic on .unwrap() of the None value.

Now gracefully returns false (update rejected) with a warning log when the task slot is None, preventing the scheduler from crashing.

What changes are included in this PR?

this is back-port of spiceai/spiceai#9636

Are there any user-facing changes?

…pache#23)

When an executor heartbeat times out, reset_tasks() sets task_infos[partition_id]
to None. If the executor later reconnects and sends a late status update,
update_task_info() would panic on .unwrap() of the None value.

Now gracefully returns false (update rejected) with a warning log when the
task slot is None, preventing the scheduler from crashing.

Fixes spiceai/spiceai#9636
@milenkovicm
Copy link
Copy Markdown
Contributor Author

@phillipleblanc i've back-ported this to ballista, I hope its ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants