-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 2023.0
-
Fix Version/s: None
-
Component/s: Azure, Elasticsearch
-
Tags:
When Nuxeo LTS 2023 is configured with the package microsoft-azure-online-storage (and the embedded ES is kept), the startup fails with the following error
ERROR [RegistrationInfoImpl] Component service:org.nuxeo.elasticsearch.ElasticSearchComponent notification of application started failed: availableProcessors is already set to [16], rejecting [16] java.lang.IllegalStateException: availableProcessors is already set to [16], rejecting [16] at io.netty.util.NettyRuntime$AvailableProcessorsHolder.setAvailableProcessors(NettyRuntime.java:51) ~[netty-common-4.1.113.Final.jar:4.1.113.Final] at io.netty.util.NettyRuntime.setAvailableProcessors(NettyRuntime.java:87) ~[netty-common-4.1.113.Final.jar:4.1.113.Final] at org.opensearch.transport.netty4.Netty4Utils.setAvailableProcessors(Netty4Utils.java:74) ~[transport-netty4-client-1.3.19.jar:1.3.19] at org.opensearch.transport.netty4.Netty4Transport.<init>(Netty4Transport.java:136) ~[transport-netty4-client-1.3.19.jar:1.3.19] at org.opensearch.transport.Netty4Plugin.lambda$getTransports$0(Netty4Plugin.java:110) ~[transport-netty4-client-1.3.19.jar:1.3.19] at org.opensearch.node.Node.<init>(Node.java:724) ~[opensearch-1.3.19.jar:1.3.19] at org.nuxeo.elasticsearch.core.PluginConfigurableNode.<init>(PluginConfigurableNode.java:35) ~[nuxeo-elasticsearch-core-2023.16.12.jar:?] at org.nuxeo.elasticsearch.core.ElasticSearchEmbeddedNode.start(ElasticSearchEmbeddedNode.java:97) ~[nuxeo-elasticsearch-core-2023.16.12.jar:?] at org.nuxeo.elasticsearch.core.ElasticSearchAdminImpl.connect(ElasticSearchAdminImpl.java:142) ~[nuxeo-elasticsearch-core-2023.16.12.jar:?] at org.nuxeo.elasticsearch.core.ElasticSearchAdminImpl.<init>(ElasticSearchAdminImpl.java:123) ~[nuxeo-elasticsearch-core-2023.16.12.jar:?] at org.nuxeo.elasticsearch.ElasticSearchComponent.start(ElasticSearchComponent.java:182) ~[nuxeo-elasticsearch-core-2023.16.12.jar:?] at org.nuxeo.runtime.model.impl.RegistrationInfoImpl.start(RegistrationInfoImpl.java:350) [nuxeo-runtime-2023.14.23.jar:?] at org.nuxeo.runtime.model.impl.ComponentManagerImpl.startComponent(ComponentManagerImpl.java:742) [nuxeo-runtime-2023.14.23.jar:?] at org.nuxeo.runtime.model.impl.ComponentManagerImpl.startComponents(ComponentManagerImpl.java:724) [nuxeo-runtime-2023.14.23.jar:?] at org.nuxeo.runtime.model.impl.ComponentManagerImpl.start(ComponentManagerImpl.java:825) [nuxeo-runtime-2023.14.23.jar:?]
The issue does not happen when Nuxeo is started against a standalone Elasticsearch