You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/08/27 17:40:35 UTC

[GitHub] [arrow-ballista] andygrove opened a new issue, #165: No scheduler logs when deployted to k8s

andygrove opened a new issue, #165:
URL: https://github.com/apache/arrow-ballista/issues/165

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   According to the user guide, it should be possible to see scheduler logs:
   
   ```
   $ kubectl logs ballista-scheduler-0
   [2021-02-19T00:24:01Z INFO  scheduler] Ballista v0.7.0 Scheduler listening on 0.0.0.0:50050
   [2021-02-19T00:24:16Z INFO  ballista::scheduler] Received register_executor request for ExecutorMetadata { id: "b5e81711-1c5c-46ec-8522-d8b359793188", host: "10.1.23.149", port: 50051 }
   [2021-02-19T00:24:17Z INFO  ballista::scheduler] Received register_executor request for ExecutorMetadata { id: "816e4502-a876-4ed8-b33f-86d243dcf63f", host: "10.1.23.150", port: 50051 }
   ```
   
   However, I just tried this, and there is no logging.
   
   We should update the user guide to explain how to enable logging or maybe enable it in the provided yaml.
   
   **Describe the solution you'd like**
   None
   
   **Describe alternatives you've considered**
   None
   
   **Additional context**
   None
   


-- 
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-ballista] mingmwang commented on issue #165: No scheduler logs when deployed to k8s

Posted by GitBox <gi...@apache.org>.
mingmwang commented on issue #165:
URL: https://github.com/apache/arrow-ballista/issues/165#issuecomment-1236325504

   I think the log was saved to files, it is not output to stdout anymore. @Ted-Jiang 
   
   


-- 
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

[GitHub] [arrow-ballista] avantgardnerio commented on issue #165: No scheduler logs when deployed to k8s

Posted by GitBox <gi...@apache.org>.
avantgardnerio commented on issue #165:
URL: https://github.com/apache/arrow-ballista/issues/165#issuecomment-1229234694

   Likely need:
   
   ```
   spec:
     containers:
     - name: envar-demo-container
       image: gcr.io/google-samples/node-hello:1.0
       env:
       - name: RUST_LOG
         value: "debug"
         ```


-- 
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

[GitHub] [arrow-ballista] Ted-Jiang commented on issue #165: No scheduler logs when deployed to k8s

Posted by GitBox <gi...@apache.org>.
Ted-Jiang commented on issue #165:
URL: https://github.com/apache/arrow-ballista/issues/165#issuecomment-1236506196

   > I think the log was saved to files, it is not output to stdout anymore. @Ted-Jiang
   
   Thanks for remind me this,  I found  i miss the declaration of std-output in tokio-tracing 😂 
   I will fix this


-- 
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

[GitHub] [arrow-ballista] andygrove closed issue #165: No scheduler logs when deployed to k8s

Posted by GitBox <gi...@apache.org>.
andygrove closed issue #165: No scheduler logs when deployed to k8s
URL: https://github.com/apache/arrow-ballista/issues/165


-- 
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