narendly commented on issue #2024: URL: https://github.com/apache/helix/issues/2024#issuecomment-1092988914
@hmhagberg Thanks for explaining where the warn log was coming from. > Good info! So the warning is indeed valid and we should be creating ResourceConfig along with IdealState. Actually, that's not what I meant - that is only so if the application needs to encode more configs (other than what's required in IdealState). In such cases, a ResourceConfig must be created and the application should add the configs in ResourceConfig, not IdealState. If there aren't such extra configs, then ResourceConfig is optional. But in your case though, it seems that you are using dedicated thread pools for your resources? If so, are you creating a proper ResourceConfig and adding a thread pool size field to it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
