[GitHub] [arrow-datafusion] thinkharderdev opened a new issue, #2498: Ballista: Persistent State causes panic on scheduler restart

[GitBox <gi...@apache.org>]

thinkharderdev opened a new issue, #2498:
URL: https://github.com/apache/arrow-datafusion/issues/2498

   **Describe the bug**
   Currently, the scheduler state keeps an in-memory map from job ID to `SessionContext`. When initializing persistent state, the `SessionContext`s are not saved into storage. When the scheduler restarts it will try and initialize any jobs saved in persistent storage but will panic when it tries to find the `SessionContext` associated with the each job. 
   
   **To Reproduce**
   1. Submit a job
   2. Restart the scheduler
   3. The scheduler will immediately crash when initializing
   
   **Expected behavior**
   The `SessionContext` (or really the properties required to create a new `SessionContext`) should be serialized to persistent storage so the scheduler can resume properly on restart
   
   **Additional context**
   Add any other context about the problem here.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-datafusion] andygrove closed issue #2498: Ballista: Persistent State causes panic on scheduler restart

[GitBox <gi...@apache.org>]

andygrove closed issue #2498: Ballista: Persistent State causes panic on scheduler restart
URL: https://github.com/apache/arrow-datafusion/issues/2498


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org