Skip to content

Conversation

@suchenglong
Copy link
Contributor

Description

Users may forget to close sessions. Such idle connections lead to a waste of server resource and in the worst case, take up all the memory of server. Session timeout is trying to solve such problem.

#3483

Currently this feature has other problems

Once the session is cleared by session timeout, the client will not get the status, when client tries to use the session again, server will throw NPE. We should throw connect exception here to client, so that session pool can catch it and uses another session to connect.
Metric module will insert data to IoTDB, we need to consider use session pool in this module.


This PR has:

  • added documentation for new or modified features or behaviors.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious
    for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold
    for code coverage.

Key changed/added classes (or packages if there are too many classes) in this PR

@suchenglong
Copy link
Contributor Author

fix the issue of session timeout

@liuminghui233 liuminghui233 changed the title IOTDB-3943 [IOTDB-3943] Optimize session timeout feature Jul 26, 2022
@liuminghui233 liuminghui233 changed the title [IOTDB-3943] Optimize session timeout feature [To rel/0.13] [IOTDB-3943] Optimize session timeout feature Jul 26, 2022
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, this is your first pull request in IoTDB project. Thanks for your contribution! IoTDB will be better because of you.

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.

3 participants