You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/01/14 12:32:29 UTC

[GitHub] [dolphinscheduler] zwZjut opened a new issue #8052: [Feature][dolphinscheduler-server] master and worker Network interaction : 3 time->2 time

zwZjut opened a new issue #8052:
URL: https://github.com/apache/dolphinscheduler/issues/8052


   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   [Feature][dolphinscheduler-server]  master and worker  Network interaction : 3 time->2 time
   
   ### Use case
   
   [Feature][dolphinscheduler-server]  master and worker  Network interaction : 3 time->2 time
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

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



[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #8052: [Feature][dolphinscheduler-server] master and worker Network interaction : 3 time->2 time

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #8052:
URL: https://github.com/apache/dolphinscheduler/issues/8052#issuecomment-1013079666


   Hi:
   * Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
   * In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
   * If you haven't received a reply for a long time, you can subscribe to the developer's email,Mail subscription steps reference https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

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



[GitHub] [dolphinscheduler] caishunfeng commented on issue #8052: [Feature][dolphinscheduler-server] master and worker network interaction

Posted by GitBox <gi...@apache.org>.
caishunfeng commented on issue #8052:
URL: https://github.com/apache/dolphinscheduler/issues/8052#issuecomment-1015020887


   improvements:
   - network interactions (normal/abnormal)  
   - use async send instead of sync
   - retry strategy (now we use cache list everywhere, maybe it should sink to the communication layer)


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

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



[GitHub] [dolphinscheduler] caishunfeng commented on issue #8052: [Feature][dolphinscheduler-server] master and worker network interaction

Posted by GitBox <gi...@apache.org>.
caishunfeng commented on issue #8052:
URL: https://github.com/apache/dolphinscheduler/issues/8052#issuecomment-1016393888


   ![task_network_interaction](https://user-images.githubusercontent.com/11962619/150123559-b7facb09-482c-4d88-9574-fbc531761763.png)
   
   I found some optimization of task network interaction:
   1. worker use a unified task cache in memory, and reply looply in a interval if task change.
   2. each time the worker reply task with the whole task info and version, so that master can ignore the low version when the high version task info arrive early.


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

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