iotdb
iotdb copied to clipboard
Avoid CN OOM by Pulling User/Roles to DN When Cache Misses.
When there is no User Cache on the DN side, the entire time series will be handed over to CN for authentication, which ultimately leads to CN OOM in some PIPE scenarios with a large number of time series. To solve this problem, it is necessary to prohibit passing all time series to CN during authentication, and instead pull the user and it's corresponding roles to dn when the user cache and role caches fail.
And, how is this PR related to PIPE?
Avoid using force-push, which will mix your new changes with the old ones. This forces me to go through the whole changes again, wasting some time.