Inconsistent NDB Stored User Management When User Modified from a Different SQL Node to Where it was Created (Doc ID 2879385.1)

Last updated on JUNE 26, 2022

Applies to:

Symptoms

On : 8.0 version, Miscellaneous

ACTUAL BEHAVIOR
---------------

When dropped from the second node it does not remove the stored user from first node.
When dropped from the first node it removes the user from both nodes.
It seems the user has to be dropped from the same node to work as expected.

It was also noted that doing GRANT ALL PRIVILEGES gave the expected behaviour.

EXPECTED BEHAVIOR
-----------------------
When dropped, the stored user should be removed from all the SQL nodes in the cluster regardless of the standard GRANT privileges.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a working NDB Cluster with at least two SQL nodes
2. CREATE USER on first SQL node, GRANT specific privileges and then GRANT NDB_STORED_USER to distribute the user
3. DROP USER created from a different SQL node

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get proper distributed users across all SQL nodes.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.