-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Duplicated dbid in redis multi-instances causes error #5351
Comments
The |
we need the dbid unique to go ahead with current multidb warmboot design. |
Any case we must use duplicated dbids? |
not really a case, we found we have to use unique dbid for new db in new redis instance and assign it unique id, @lguohan raised a concern why the dbid is unique for the db in different redis instance. |
Description
Ideally dbid in different redis instances can be duplicated, but due to following code:
const TableNameSeparatorMap TableBase::tableNameSeparatorMap = { { APPL_DB, TABLE_NAME_SEPARATOR_COLON }, { ASIC_DB, TABLE_NAME_SEPARATOR_COLON }, { COUNTERS_DB, TABLE_NAME_SEPARATOR_COLON }, { LOGLEVEL_DB, TABLE_NAME_SEPARATOR_COLON }, { CONFIG_DB, TABLE_NAME_SEPARATOR_VBAR }, { PFC_WD_DB, TABLE_NAME_SEPARATOR_COLON }, { FLEX_COUNTER_DB, TABLE_NAME_SEPARATOR_COLON }, { STATE_DB, TABLE_NAME_SEPARATOR_VBAR }, { GB_ASIC_DB, TABLE_NAME_SEPARATOR_VBAR }, { GB_COUNTERS_DB, TABLE_NAME_SEPARATOR_VBAR }, { GB_FLEX_COUNTER_DB, TABLE_NAME_SEPARATOR_VBAR }, { GLOBAL_APP_DB, TABLE_NAME_SEPARATOR_VBAR } };
dup dbid in different instances will cause problem.
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: