Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Managing super_read_only variable. #376

Closed
theTibi opened this issue Jan 15, 2018 · 2 comments
Closed

Managing super_read_only variable. #376

theTibi opened this issue Jan 15, 2018 · 2 comments

Comments

@theTibi
Copy link

theTibi commented Jan 15, 2018

Hi,

Would be possible to manage super_read_only variable by Orchestrator, just like read_only,
Another layer of security to make sure nobody can write the slaves.

Does Orchestrator work if super_read_only is enabled?

Super_read_only was introduced in MySQL 5.7.8 and Percona Server 5.6.21-70. It is not available in MariaDB.

Thanks,
Tibi

@shlomi-noach
Copy link
Collaborator

shlomi-noach commented Jan 17, 2018

Does Orchestrator work if super_read_only is enabled?

It should; it doesn't write anything to the database itself.

I'm wondering how this should be approached. Should orchestrator set super_read_only whenever we set _read_only? And vice versa? Should this be controlled via configuration flag UseSuperReadOnly: true?

@theTibi
Copy link
Author

theTibi commented Jan 17, 2018

I would definitely like to see a configuration flag like you mentioned: UseSuperReadOnly: true
In that case the customers could control it how they want to use this variable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants