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

Reset or Shutdown the ConnectorRegistry #1687

Closed
hessjcg opened this issue Nov 13, 2023 · 0 comments · Fixed by #1688 or #1612
Closed

Reset or Shutdown the ConnectorRegistry #1687

hessjcg opened this issue Nov 13, 2023 · 0 comments · Fixed by #1688 or #1612
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@hessjcg
Copy link
Collaborator

hessjcg commented Nov 13, 2023

Feature Description

An application should use the public Java API to either shut down or reset the connector registry. Update the methods
as follows:

  • ConnectorRegistry.shutdown() - Stops all threads, clears all config, and causes future attempts to connect will fail.
  • ConnectorRegistry.reset() - Stops all threads, clears all config, future attempts to connect will start a new Connector.

An application would use shutdown() when it receives a callback to gracefully stop itself. The application would then have gracefully stop all its background processes. The application calls shutdown() so that if some all other background threads cannot start a database connection after ConnectorRegistry.shutdown() is called.

An application would use reset() when it needs to reload its configuration. This would gracefully close all Connector instances, causing them to reload on the next connection attempt.

Sample code

No response

Alternatives Considered

No response

Additional Details

No response

@hessjcg hessjcg added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Nov 13, 2023
@hessjcg hessjcg self-assigned this Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
1 participant