None of the configured nodes are available: [{#transport#-1}{puy-A4GASkC9mIctzxN9pQ}{192.168.163.131

已于 2022-10-23 11:55:03 修改
阅读量610 收藏 1
点赞数
文章标签： elasticsearch java 大数据
于 2022-10-23 11:53:47 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_38407312/article/details/127472797
版权

None of the configured nodes are available: [{#transport#-1}{puy-A4GASkC9mIctzxN9pQ}{192.168.163.131}{192.168.163.131:9300}]

org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{puy-A4GASkC9mIctzxN9pQ}{192.168.163.131}{192.168.163.131:9300}]
	at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:349) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:247) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:60) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:381) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:407) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:396) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.execute(AbstractClient.java:1254) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.support.AbstractClient$IndicesAdmin.exists(AbstractClient.java:1276) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.springframework.data.elasticsearch.core.ElasticsearchTemplate.indexExists(ElasticsearchTemplate.java:656) ~[spring-data-elasticsearch-3.1.9.RELEASE.jar:3.1.9.RELEASE]
	at org.springframework.data.elasticsearch.core.ElasticsearchTemplate.createIndexIfNotCreated(ElasticsearchTemplate.java:948) ~[spring-data-elasticsearch-3.1.9.RELEASE.jar:3.1.9.RELEASE]
	at org.springframework.data.elasticsearch.core.ElasticsearchTemplate.createIndex(ElasticsearchTemplate.java:195) ~[spring-data-elasticsearch-3.1.9.RELEASE.jar:3.1.9.RELEASE]
	at com.shopfreely.search.service.impl.ESManagerServiceImpl.createMappingAndIndex(ESManagerServiceImpl.java:41) ~[classes/:na]
	at com.shopfreely.search.controller.ESManagerController.create(ESManagerController.java:27) ~[classes/:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_333]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_333]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_333]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_333]
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:892) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:797) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1039) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) ~[spring-webmvc-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:92) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:93) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:109) ~[spring-web-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) ~[tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:853) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1587) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_333]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_333]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.21.jar:9.0.21]
	at java.lang.Thread.run(Thread.java:750) [na:1.8.0_333]

springboot 集成 elasticsearch 出现上面错误，主要原因是 springboot 的版本和 elasticsearch 版本不匹配造成的。
下面是 springboot 和 elasticsearch 的版本对应表
版本对应表
请对照上面表，更改 springboot 或 elasticsearch 的版本

Apa_Lagi
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
SpringBoot项目连接ElasticSearch时报错：None of the configured nodes are available
人如墨的博客
04-25 1万+
问题描述： 在springboot项目中使用TransportClient方式连接ES，完整报错： org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available 背景 SpringBoot版本：1.5.11 ES版本：7.0.0 项目中配置文件： ...
NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}····
牛大春の博客
01-20 4205
最近一直在搞一个与Spring Boot相关的项目，由于我的Elasticsearch并不是在本地Window中的，而是配置在Linux虚拟机中，然后就遇到了这样的一个错误： NoNodeAvailableException[None of the configured nodes are available: 什么意思呢？翻译过来就是：配置的节点均不可用 可是，我明明可以通过Window的浏览器端进行访问的，如下图： 因为9200是给浏览器进行测试访问的，然后9300是给Java这种后端语言来进行访问
11
carrots
06-12 344
Exception in thread "main" NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{fnXsQzMSThmJ_s8pKVnZng}{localhost}{127.0.0.1:9300}]] at org.elasticsearch.client.transp...
这些年遇到的Java连接ES报错原因汇总 ＞＞ None of the configured nodes are available:[{#transport#-1}{jfVEwfw7QJqo1VW
健身变秃，coding变强
01-13 5832
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{127.0.0.1:9300}] 以及：Caused by: java.lang.IllegalStateException: availableProcessors is already set to [4], rejecting [4]
None of the configured nodes are available: [{#transport#-1}{erAdMJ4wTNGxixzYoTGhCw}
chouzini2469的博客
05-03 1714
使用java api和elasticsearch进行交互时，进行到如下代码编写: data: elasticsearch: repositories: enabled: true cluster-nodes: 127.0.0.1:9300 ...
elasticsearch报错:None of the configured nodes are available: []
weixin_30565199的博客
04-27 405
问题:在内网测试的时候可以正常访问，但是部署到外网上客户端连接elasticsearch报错:None of the configured nodes are available: [] 原因:默认情况下，ElasticSearch使用0.0.0.0地址，并为http传输开启9200-9300端口，为节点到节点的通信开启9300-9400端口,部署到外网修改修改elastic...
ES问题 NoNodeAvailableException: None of the configured nodes are available 原因是集群名字写错了
lilyssh的博客
04-27 781
遇到异常： cn.xxxx.op.points.aop.GlobalExceptionHandler - 捕获到Exception异常 org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{1BDQ_cF9QDaalAYFvwzZ8g}{10.58.124.4}{10.58.124.4:9300}] at org.el
Java调用Elasticsearch Api报错：NoNodeAvailableException: None of the configured nodes are available
学而不思则罔 思而不学则殆
10-08 2009
项目需要最近安装配置elasticsearch，在安装和配置过程中遇到了好几个问题，记录下来希望能给大家提供一些解决办法或解决方案 1、在使用Java程序连接elasticsearch时，控制台报错：org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are avai...
Docker 安装ElasticSearch 启动项目出现 [{#transport#-1}{WW73fQYgSq-vd8jQXTmdIw}{192.168.11.134}{192.168.11.13
NULL
11-27 1226
1), docker 安装 elasticSearch 如下 docker run -di --name=tensquare_es -p 9200:9200 -p 9300:9300 elasticsearch:5.6.8 2),通过如下命令 查看是否成功 docker ps 3),页面访问 elasticsearch 是否成功 4), ...
None of the configured nodes are availableException错误解决
刘大磊的博客
09-03 5394
1.利用TransportClient对elastic进行操作时，报错如下 2.问题原因： @SuppressWarnings({ "unchecked", "resource" }) public static void main(String[] args) throws Exception { // 先构建client Settings settings = Setting
spring boot连接ES异常报错：None of the configured nodes are available
企业实战系列集 ●●● https://ximenjianxue.blog.csdn.net
05-16 5135
一、问题描述 某次监控项目里，后端数据分析组件启动时，catalina日志报错无法连接ES，显示所有ES当前状态不可用，报错如下： 2022-05-16 10:18:57.667 [localhost-startStop-1] ERROR c.u.a.q.QuartzJobBaseLineBean - org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available:
SpringBoot连接Elasticsearch报错:None of the configured nodes are available
build_zzz的博客
07-16 644
SpringBoot连接Elasticsearch报错:None of the configured nodes are available: 最近在借鉴别人的项目的时候，项目中使用到了Elasticsearch,本来是想在Linux在安装的，但是需要改的东西太多了。如果实在需要在Linux下安装，遇到错误的话，可以参看下面的连接（主要是启动的错误）： [https://www.cnblogs.com/zhi-leaf/p/8484337.html] 回到正题，本人真实经历是在Linux下启动成功了，但是s
NoNodeAvailableException[None of the configured nodes are available
weixin_44874132的博客
09-29 867
由于前段时间使用SpringBoot连接ES6.5使用的不亦乐乎，如今发现7.x以后的kibana中Dev Tools对中文支持相比较于6.x时代好了几个时代，果断将ES环境切到7.x，但问题也随之而来了。 此处记录一下使用springboot的工具spring-boot-starter-data-elasticsearch操作ES时遇到的坑， 正常创建索引时控制台报错log： NoNodeAvailableException[None of the configured nodes are availab
None of the configured nodes are available
星星绿茶的博客
10-19 990
使用elasticsearch java api 调用es服务时出现NoNodeAvailableException的错误时原因有下： Settings esSetting = Settings.builder().put("cluster.name", "elasticsearch").build(); TransportClient client = new PreBuiltTransport
NoNodeAvailableException: None of the configured nodes are available(elasticsearch报错)
枸杞泡茶的博客
04-20 1001
出现这种错误的原因是有多种的,可能是你的elasticsearch没有启动成功,又或者是network.host没有对外开发,这里我说下我遇到的问题. elasticsearch的配置文件配置在config目录下的elasticsearch.yml文件中 elasticsearch默认的端口为9200和9300 9200是对外开发的端口 9300是集群节点通讯的端口 当我们在java程序...
None of the configured nodes are available: [{#transport#-1}{3DJiAGl3Qo-mzWGpEZB08w}{127.0.0.1}{127.0.0.1:9191}]
最新发布
04-04
这个错误提示表明配置的节点都不可用。在这种情况下，可能有以下几个原因导致节点不可用： 1. 节点未启动：请确保节点已经正确启动并正在运行。你可以检查节点的状态和日志文件来确认。 2. 网络连接问题：如果节点是在远程服务器上运行的，可能存在网络连接问题。请确保你能够正常访问节点所在的服务器，并且网络连接没有问题。 3. 配置错误：检查配置文件中节点的配置是否正确。确保IP地址、端口号等信息都正确配置。 4. 节点故障：如果节点出现故障或崩溃，可能会导致节点不可用。在这种情况下，你需要重新启动节点或修复故障。 如果以上方法都无法解决问题，建议你查看相关文档或寻求技术支持以获取更详细的帮助。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值