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

Enhance transactional message implementation #396

Closed
duhengforever opened this Issue Aug 8, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@duhengforever
Member

duhengforever commented Aug 8, 2018

In order to avoid the interaction between ordinary message and transactional messages,therefore it is recommended to use separate thread pools. and related watermark monitoring and runtime information acquisition are also required.

vongosling added a commit that referenced this issue Aug 17, 2018

[ISSUE #396]Use separated thread pool and add monitor tools for trans…
…actional message (#397)

* Use separate threadpool and add monitor tools for transaction

* Modify log level
@duhengforever

This comment has been minimized.

Show comment
Hide comment
@duhengforever

duhengforever Aug 31, 2018

Member

Merged!

Member

duhengforever commented Aug 31, 2018

Merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment