Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MINOR] Support specify timeout for AM waiting for client signal stop #518

Merged
merged 3 commits into from
Mar 26, 2021

Conversation

zuston
Copy link
Member

@zuston zuston commented Mar 24, 2021

Why

In once loop of monitorApplication method, when costing too much time over 15s , AM will finished, not waiting TonY client stop signal.
So AM rpc service will closed. But TonY client will call updateTaskInfos method, it will cause exception.

I think it's necessary to allow specify AM waiting timeout, because we extend the ClusterSubmmitter to support TaskUpdateListener, which may cost too much time in monitorApplication once loop.

@zuston
Copy link
Member Author

zuston commented Mar 24, 2021

@oliverhu Please review it. Thanks.

@oliverhu
Copy link
Member

@zuston please check the tests failures first..

@oliverhu
Copy link
Member

pls resolve the conflicts

@zuston
Copy link
Member Author

zuston commented Mar 25, 2021

@zuston please check the tests failures first..

Sorry, CI test cost too much time. Sometimes I forget checking its status.

pls resolve the conflicts

OK.

@zuston zuston closed this Mar 25, 2021
@zuston zuston reopened this Mar 25, 2021
@oliverhu oliverhu merged commit 8470968 into tony-framework:master Mar 26, 2021
zuston added a commit to zuston/TonY that referenced this pull request Apr 21, 2021
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