Ken, Wang comments

Results 66 comments of


                                            Ken, Wang

ExecutorReservation during task scheduling

@thinkharderdev

Ballista Executor report plan/operators metrics to Ballista Scheduler

@thinkharderdev @andygrove Please help to review my PR.

Ballista Executor report plan/operators metrics to Ballista Scheduler

@andygrove @thinkharderdev Can we merge this PR first? We can have ongoing PR to track the proper place for metrics and task status storage.

Ballista Executor report plan/operators metrics to Ballista Scheduler when task finish

@thinkharderdev I think we already have a RPC for the task status update. We can enhance the existing method to report task metrics to Scheduler instead of adding another RPC....

Enhance TaskContext and add task failure root cause

@yahoNanJing

Enhance TaskContext and add task failure root cause

@alamb @yahoNanJing This would help and this approach is more rusty. But it still depends on the programer to propagate the errors correctly in the execution path. And there is...

Suspicious slow test in Ballista

I had encountered the same issue in my local laptop.

Suspicious slow test in Ballista

```` 2658 Thread_8907905: cpu_bound_executor::tests::executor_shutdown_while_task_running 2658 thread_start (in libsystem_pthread.dylib) + 15 [0x7fff6f346b8b] 2658 _pthread_start (in libsystem_pthread.dylib) + 148 [0x7fff6f34b109] 2658 std::sys::unix::thread::Thread::new::thread_start::hcccd55275f17da3c (in ballista_executor-68e1b504e701a7b1) + 39 [0x1015118b7] 2658 core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::heaae50de5145d63f (in ballista_executor-68e1b504e701a7b1) +...

Suspicious slow test in Ballista

Can we upgrade the tokio version in Ballista ?

Make fetch shuffle partition data in parallel

@yahoNanJing Could you please explain a little about the error handling case ? For example, if one of the parallel fetch failed, what happened to the others ? And what...