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

Publish new task asynchronously, configure independent thread pool current limit #51

Closed
Synex-wh opened this issue Sep 19, 2019 · 0 comments

Comments

@Synex-wh
Copy link
Contributor

Describe the bug

  • Since the renew function requires that the pub addition is not successful after the dataserver is synchronized, the synchronization process is asynchronous, and the original data access queue pool AccessorExecutor is disabled.
  • For the case where the client playback traffic is huge, the new post task must be configured with independent threads for current limiting.

Modify

  • Configure an independent thread pool for asynchronous execution of the pub synchronization dataserver task to ensure that the task receives normal, and corrects the overnew error waiting for the renew task.
  • For the access test, all new Token bucket flow control is set, currently 10w cards are set, and subsequent restrictions are based on traffic.
@dzdx dzdx closed this as completed Mar 16, 2022
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

No branches or pull requests

2 participants