-
Notifications
You must be signed in to change notification settings - Fork 265
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
Check for service name too long at subCacheRefresh #2848
Comments
Not sure... The issue is pretty old (more than 7 years) but probably it's still valid. Reading the old description, it seems to be a minor thing, so maybe it is easy to implement. I'd suggest you to create the pull request and let's see at that moment the suitability of the fix or not. What do you think? |
Thanks for response. Started investigation, will add PR. Just to confirm my issue understanding:
|
Yes, I think you are right. Not sure what to do in the "false" case. Some options:
I think we should go for option 2. |
As reference, longest case in production environment of |
PR #4297 |
A recent fix (#2812) makes sure that the name of a tenant (service) cannot be more than 44 chars, depending on the prefix ('orion-' by default - 44 is for the default prefix).
However, prior to this fix, the broker did accept tenants of up to 50 chars and so, old databases may reside on the harddisk with a total database name of up to 61 chars (as max longitud for the prefix is 10, not including the hyphen).
subCacheRefresh asks
bool getOrionDatabases(std::vector<std::string>& dbs)
in mongoBackend/MongoGlobal.cpp for the list of databases and to complete the fix in #2812, we should probably add a check in getOrionDatabases for databases with long names (> 50 chars in total, prefix included).The text was updated successfully, but these errors were encountered: