Skip to content

Catch ETS exception when system is still starting #10375

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

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

acogoluegnes
Copy link
Contributor

Because the ETS table may be not created yet.
A stream connection can call another node to
get the port of the stream plugin on this node.
The stream plugin uses the rabbit_networking module, which relies on an ETS table to store listener information. The table may be not created yet when the node starts up, so the calling node ends up logging a large stack trace.

This commit catches the exception and logs a simple message. This reduces unnecessary noise in the logs.

Because the ETS table may be not created yet.
A stream connection can call another node to
get the port of the stream plugin on this node.
The stream plugin uses the rabbit_networking module,
which relies on an ETS table to store listener information.
The table may be not created yet when the node starts up,
so the calling node ends up logging a large stack trace.

This commit catches the exception and logs a simple message.
This reduces unnecessary noise in the logs.
@acogoluegnes acogoluegnes added this to the 3.13.0 milestone Jan 19, 2024
@michaelklishin michaelklishin merged commit 9b884bb into main Jan 19, 2024
@michaelklishin michaelklishin deleted the catch-ets-exception-on-startup branch January 19, 2024 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants