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

Client fast chain breakage data can not be cleaned up #37

Open
Synex-wh opened this issue Jun 28, 2019 · 0 comments
Open

Client fast chain breakage data can not be cleaned up #37

Synex-wh opened this issue Jun 28, 2019 · 0 comments

Comments

@Synex-wh
Copy link
Contributor

@Synex-wh Synex-wh commented Jun 28, 2019

Describe the bug

The client fast chain break does not trigger the clientoff operation to delete data, causing garbage data to exist and push the client.

analysis

  • The query corresponds to ip and port does have a broken link record. Note that this link and broken link are triggered in unified seconds, which is a flash situation.

image

  • During the flash, the client made the pub data and successfully synchronized to the data.
    image

  • By breaking the link and initiating the clientoff log, you can see that the pub sub wat memory that was queried at the time of the initiation is not stored, and all are false. This situation should be the new data pub has not come to the end of the dataserver to return, and then write the memory to start the clientoff, so the query will not launch the clientoff will not be able to clean up this data

solution

  • It is necessary to periodically check that the link does not exist but the memory data and the corresponding data are periodically cleaned up by the client.

  • SOFARegistry version:5.2.0

  • JVM version (e.g. java -version):

  • OS version (e.g. uname -a):

  • Maven version:

  • IDE version:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.