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

Change ETS queue table permissions to protected #782

Merged
merged 1 commit into from
Apr 10, 2018

Conversation

russelldb
Copy link
Member

NOTE: opened to replace #781

Sometimes realtime replication stops working, the reason why it has stopped is unclear, diagnosis is further complicated by the fact that the ETS queue table (buffer of objects due to be replicated to the sink) is private (can only be seen by the riak_repl2_rtq gen_server instance).

If it were possible to examine the contents of that table the support engineer could examine the queued objects and perhaps discover that there is a large object causing head of line blocking. At the moment the only option is to kill the process and let the supervisor restart it, destroying all useful information in the process. The diagnostic information is opaque and needlessly so.

The table doesn't need to be changed to public as it's probably undesirable to modify state outside the public API for this gen_server.

I propose that the permissions be changed to 'protected' in order to improve visibility.

Sometimes realtime replication stops working, the reason why it has stopped is unclear, diagnosis is further complicated by the fact that the ETS queue table (buffer of objects due to be replicated to the sink) is private (can only be seen by the `riak_repl2_rtq` `gen_server` instance).

If it were possible to examine the contents of that table the support engineer could examine the queued objects and perhaps discover that there is a large object causing head of line blocking. At the moment the only option is to kill the process and let the supervisor restart it, destroying all useful information in the process. The diagnostic information is opaque and needlessly so.

The table doesn't need to be changed to public as it's probably undesirable to modify state outside the public API for this gen_server.

I propose that the permissions be changed to 'protected' in order to improve visibility.
@russelldb
Copy link
Member Author

Reviewed and approved @ #781.

@russelldb russelldb merged commit 979c867 into develop-2.2 Apr 10, 2018
@russelldb russelldb deleted the binarytemple/rtc-ets-perms branch April 10, 2018 07:26
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.

1 participant