Open BrynXu opened 3 years ago
The tableNameSeparatorMap
and the constructor TableBase(int dbId, const std::string &tableName)
is going to deprecate in future, so it is suggested not to extend the map. Instead the same functionality could be achieved by database_config.json
. Could you check?
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. Per my understand, dbids from different redis instances are not relevant, redis allows duplication among them, it is current sonic code introduces the unique id requirement, it is better to indicate this in doc for redis multi-instance developers.
Description Ideally dbid in different redis instances can be duplicated, but due to following code:
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):