티스토리 뷰
ES Java client 사용시 availableProcessors is already set to [8], rejecting [8] 발생
Mr. Curious 2017. 10. 31. 19:14netty를 사용하는 모듈과 충돌이 발생하는 경우이다.
Elasticsearch client 초기화 시점을 앞당기거나 system property es.set.netty.runtime.available.processors 를 false로 세팅해서 해결한다.
java.lang.IllegalStateException: availableProcessors is already set to [8], rejecting [8]
at io.netty.util.NettyRuntime$AvailableProcessorsHolder.setAvailableProcessors(NettyRuntime.java:51)
at io.netty.util.NettyRuntime.setAvailableProcessors(NettyRuntime.java:87)
at org.elasticsearch.transport.netty4.Netty4Utils.setAvailableProcessors(Netty4Utils.java:87)
at org.elasticsearch.transport.netty4.Netty4Transport.<init>(Netty4Transport.java:139)
at org.elasticsearch.transport.Netty4Plugin.lambda$getTransports$0(Netty4Plugin.java:93)
at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:174)
at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:265)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:130)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:116)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:106)
at kr.bluewhale.elastic.broker.ElasticQueryThread.run(ElasticQueryThread.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
System.setProperty("es.set.netty.runtime.available.processors", "false");
'Programming > ElasticSearch' 카테고리의 다른 글
특정인덱스의 field 값을 distinct하게 뽑아 내기 (772) | 2017.12.19 |
---|---|
Elasticsearch Java client DSL로 작성한 Request의 실제 Query 확인하기 (0) | 2017.11.01 |
Elasticsearch java client 사용시 java.lang.NoClassDefFoundError: org/elasticsearch/plugins/NetworkPlugin 발생하는 경우 (0) | 2017.10.31 |
인덱스 안의 모든 타입의 xxx field의 fielddata를 true로 세팅 (402) | 2017.10.27 |
no [query] registered for [filtered] 오류가 나며 filtered query가 에러나는 경우 (0) | 2017.10.25 |
- Total
- Today
- Yesterday
- AWS
- IntelliJ
- Python
- ansible-container
- GCP
- pycharm
- Paw
- zsh
- xpath
- docker
- TDD
- Ansible
- Elasticsearch
- scrapy
- MongoDB
- X-Pack
- PubSub
- Spring Boot
- git
- spring #lombok
- PIP
- mecab
- MacOS
- Redis
- docker-machine
- Netty
- kubernetes
- 은전한닢
- boot2docker
- pymongo
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |