-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Add undeclared Azure settings, modify test to exercise them #118634
Add undeclared Azure settings, modify test to exercise them #118634
Conversation
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
I added tests that two of the settings are effective when set, the remaining ones don't seem to be easily testable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think this should be labelled as >bug
instead? It has a visible impact and also could use a doc update.
Being able to registering all these settings is already a test. So I am not too worried about testing whether the remaining two getting picked up by the connectionProvider.
ThreadPool nodeThreadPool = internalCluster().getInstance(ThreadPool.class); | ||
assertEquals( | ||
EVENT_LOOP_THREAD_COUNT_SETTING.get(), | ||
((EsThreadPoolExecutor) nodeThreadPool.executor(AzureRepositoryPlugin.NETTY_EVENT_LOOP_THREAD_POOL_NAME)).getMaximumPoolSize() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: can this be
nodeThreadPool.info(AzureRepositoryPlugin.NETTY_EVENT_LOOP_THREAD_POOL_NAME).max()
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's much nicer, thanks. Used in a0eaa92
Hi @nicktindall, I've created a changelog YAML for you. |
Declares some settings that were undeclared by the Azure repository plugin.
Specifically, this PR allows use of
repository.azure.http_client.event_loop_executor_thread_count
repository.azure.http_client.max_open_connections
repository.azure.http_client.connection_timeout
repository.azure.http_client.connection_max_idle_time