Springboot Elasticsearch 异常 | ResponseException：URI [/_cluster/health/], status line [HTTP/1.1 401

最新推荐文章于 2025-06-20 15:36:39 发布
最新推荐文章于 2025-06-20 15:36:39 发布
阅读量10w+ 收藏 5
点赞数 3
CC 4.0 BY-SA版权
分类专栏： springboot 文章标签： springboot elasticsearch 401 http 异常
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/qq_41497111/article/details/98313478
本文记录了在使用Spring Boot连接Elasticsearch时遇到的未授权访问错误，并提供了详细的解决方案，包括检查配置文件和添加正确的用户名密码。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

今天es 指定端口登录时，出现一个问题：

Caused by: org.elasticsearch.client.ResponseException: method [GET], host [http://127.0.0.1:9210], URI [/_cluster/health/], status line [HTTP/1.1 401 Unauthorized]

意思就是说，没有权限访问。

 

解决方法

查看 es 配置文件 elasticsearch.yml 发现配置了权限过滤。

ok，此时我们应该在 springboot 配置文件，加上对应的 用户名密码。再次启动，问题解决。。。。

具体信息

2019-08-03 10:29:50.742  INFO 19028 --- [           main] o.s.d.e.c.TransportClientFactoryBean     : Adding transport node : 127.0.0.1:9300
2019-08-03 10:29:52.096 ERROR 19028 --- [           main] .d.e.r.s.AbstractElasticsearchRepository : failed to load elasticsearch nodes : org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{QbWbCQA-RYmUyRTHXzuonA}{127.0.0.1}{127.0.0.1:9300}]
2019-08-03 10:29:52.363  INFO 19028 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
2019-08-03 10:29:52.430  INFO 19028 --- [           main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/v2/api-docs] onto method [public org.springframework.http.ResponseEntity<springfox.documentation.spring.web.json.Json> springfox.documentation.swagger2.web.Swagger2Controller.getDocumentation(java.lang.String,javax.servlet.http.HttpServletRequest)]
2019-08-03 10:29:52.527  INFO 19028 --- [           main] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService 'applicationTaskExecutor'
2019-08-03 10:29:52.724  INFO 19028 --- [           main] d.s.w.p.DocumentationPluginsBootstrapper : Context refreshed
2019-08-03 10:29:52.734  INFO 19028 --- [           main] d.s.w.p.DocumentationPluginsBootstrapper : Found 1 custom documentation plugin(s)
2019-08-03 10:29:52.756  INFO 19028 --- [           main] s.d.s.w.s.ApiListingReferenceScanner     : Scanning for api listing references
2019-08-03 10:29:52.876  INFO 19028 --- [           main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: searchUsingGET_1
2019-08-03 10:29:52.914  INFO 19028 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8081 (http) with context path ''
2019-08-03 10:29:52.915  INFO 19028 --- [           main] c.m.mall.search.MallSearchApplication    : Started MallSearchApplication in 5.664 seconds (JVM running for 6.138)
2019-08-03 10:29:53.169  WARN 19028 --- [169.254.211.158] o.s.b.a.e.ElasticsearchHealthIndicator   : Elasticsearch health check failed

org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{QbWbCQA-RYmUyRTHXzuonA}{127.0.0.1}{127.0.0.1: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$ClusterAdmin.execute(AbstractClient.java:708) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.support.AbstractClient$ClusterAdmin.health(AbstractClient.java:730) ~[elasticsearch-6.4.3.jar:6.4.3]
	at org.springframework.boot.actuate.elasticsearch.ElasticsearchHealthIndicator.doHealthCheck(ElasticsearchHealthIndicator.java:79) ~[spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.AbstractHealthIndicator.health(AbstractHealthIndicator.java:84) ~[spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.CompositeHealthIndicator.health(CompositeHealthIndicator.java:98) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.HealthEndpoint.health(HealthEndpoint.java:50) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_191]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_191]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
	at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:246) [spring-core-5.1.5.RELEASE.jar:5.1.5.RELEASE]
	at org.springframework.boot.actuate.endpoint.invoke.reflect.ReflectiveOperationInvoker.invoke(ReflectiveOperationInvoker.java:76) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.annotation.AbstractDiscoveredOperation.invoke(AbstractDiscoveredOperation.java:61) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:126) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:99) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [na:1.8.0_191]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) [na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_191]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_191]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [na:1.8.0_191]
	at sun.rmi.transport.Transport$1.run(Transport.java:200) [na:1.8.0_191]
	at sun.rmi.transport.Transport$1.run(Transport.java:197) [na:1.8.0_191]
	at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_191]
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [na:1.8.0_191]
	at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [na:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191]

2019-08-03 10:29:53.217  WARN 19028 --- [169.254.211.158] s.b.a.e.ElasticsearchRestHealthIndicator : Elasticsearch health check failed

org.elasticsearch.client.ResponseException: method [GET], host [http://127.0.0.1:9210], URI [/_cluster/health/], status line [HTTP/1.1 401 Unauthorized]
Unauthorized
	at org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:920) ~[elasticsearch-rest-client-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:227) ~[elasticsearch-rest-client-6.4.3.jar:6.4.3]
	at org.springframework.boot.actuate.elasticsearch.ElasticsearchRestHealthIndicator.doHealthCheck(ElasticsearchRestHealthIndicator.java:61) ~[spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.AbstractHealthIndicator.health(AbstractHealthIndicator.java:84) ~[spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.CompositeHealthIndicator.health(CompositeHealthIndicator.java:98) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.health.HealthEndpoint.health(HealthEndpoint.java:50) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_191]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_191]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
	at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:246) [spring-core-5.1.5.RELEASE.jar:5.1.5.RELEASE]
	at org.springframework.boot.actuate.endpoint.invoke.reflect.ReflectiveOperationInvoker.invoke(ReflectiveOperationInvoker.java:76) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.annotation.AbstractDiscoveredOperation.invoke(AbstractDiscoveredOperation.java:61) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:126) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at org.springframework.boot.actuate.endpoint.jmx.EndpointMBean.invoke(EndpointMBean.java:99) [spring-boot-actuator-2.1.3.RELEASE.jar:2.1.3.RELEASE]
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [na:1.8.0_191]
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401) [na:1.8.0_191]
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829) [na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_191]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_191]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_191]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [na:1.8.0_191]
	at sun.rmi.transport.Transport$1.run(Transport.java:200) [na:1.8.0_191]
	at sun.rmi.transport.Transport$1.run(Transport.java:197) [na:1.8.0_191]
	at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_191]
	at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [na:1.8.0_191]
	at java.security.AccessController.doPrivileged(Native Method) [na:1.8.0_191]
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [na:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_191]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_191]
	at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191]
Caused by: org.elasticsearch.client.ResponseException: method [GET], host [http://127.0.0.1:9210], URI [/_cluster/health/], status line [HTTP/1.1 401 Unauthorized]
Unauthorized
	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:540) ~[elasticsearch-rest-client-6.4.3.jar:6.4.3]
	at org.elasticsearch.client.RestClient$1.completed(RestClient.java:529) ~[elasticsearch-rest-client-6.4.3.jar:6.4.3]
	at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:122) ~[httpcore-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:181) ~[httpasyncclient-4.1.4.jar:4.1.4]
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:448) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:338) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) ~[httpasyncclient-4.1.4.jar:4.1.4]
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) ~[httpasyncclient-4.1.4.jar:4.1.4]
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) ~[httpcore-nio-4.4.11.jar:4.4.11]
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) ~[httpcore-nio-4.4.11.jar:4.4.11]
	... 1 common frames omitted

2019-08-03 10:29:53.229  INFO 19028 --- [169.254.211.158] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2019-08-03 10:29:53.229  INFO 19028 --- [169.254.211.158] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2019-08-03 10:29:53.237  INFO 19028 --- [169.254.211.158] o.s.web.servlet.DispatcherServlet        : Completed initialization in 8 ms

 

 

【异常】ES报错ResponseException: method [HEAD], host [], URI [/], status line [HTTP/1.1 401 Unauthorized]
本本本添哥
03-21 4155
以上代码想要建立与ES的连接，并且创建ES客户端来实现对ES中的索引操作，但是因为登录到ES，ES启用了账号密码的模式，因此必须要使用账号密码才能够访问它。修改代码，增加账号密码即可。
【项目实战】SpringBoot连接ES报错status line [HTTP/1.1 401 Unauthorized
本本本添哥
03-15 4507
SpringBoot的配置文件yaml中与ES连接的配置内容如下。直接将SpringBoot的配置文件yaml文件，修改成以下即可。可以很明显看到，无法找到使用，可是我明明已经引入了ES的依赖了。有教程说在application.yml中添加。因为账号密码错误，导致了无法连接ES，提示。这个是错的，已经被弃用的使用方式了。修改完成后，可以正常看到系统源码的。
org.elasticsearch.client.ResponseException
weixin_42602368的博客
01-07 2724
org.elasticsearch.client.ResponseException 是 Java 中 Elasticsearch 客户端类库中的一个异常类。这个异常表示在 Elasticsearch 服务器端发生了某些错误，并且服务器返回了一个非正常的 HTTP 响应。可能的原因包括 Elasticsearch 服务器内部发生了错误，或者用户发送的请求不合法等。如果你在使用 Elasticsea...
elasticsearch报错AuthenticationException(401, ‘security_exception‘,‘unable to authenticate user
最新发布
lzcs1的博客
06-20 506
es报标题的错时，9200端口的认证页面虽然可以打开，但没法登录，也就是。.security-7没法正常生成。kibana此时会报错。
【elsctic】elsctic kerberos status line [HTTP/1.1 401 Unauthorized] authenticate failed!
九师兄
06-28 1946
elsctic远程认证kerberos集群 我同事的正常，但是我的不正常我的配置信息如下 我把我的代码放到对方集群的某个机器上，同样的配置，对方就可以，但是我的不行。es认证代码如下 具体认证的代码如下 远程服务器打印如下，并且没有报错 但是我放到集群之外的服务器报错 如下 然后此时代码是这样的 最后找到原因了，然后改成这样就可以了 后来验证好像不是这个问题,好像是 这个名称些错误了 应该是这样的 打印日志如下 然后就好了,这个完全就是编码不执行，一个细节导致的错误，但是找了一个下午，耗时 4个多小时..
SpringBoot整合es提示错误：ElasticsearchException[Invalid or missing build flavor [oss]]
我还可以
07-12 6172
SpringBoot整合es提示错误：ElasticsearchException[Invalid or missing build flavor [oss]]问题属于Springboot中引入的es版本与es服务版本不一致导致，当前项目引入es版本为，服务器版本为，版本修改统一即可；
SpringBoot访问接口出现401
a45622678的博客
07-03 2946
SpringBoot访问接口出现401并且没有错误日志出现。在.excludePathPatterns()中配置不需要拦截器的地址即可。修改完以上两个问题，便可以访问接口成功。拦截器将访问接口拦截，所以出现401。网上查阅项目的pom.xml中多了。的jar包，去掉这个jar包就好了。
spring boot admin抛出“status“:401,“error“:“Unauthorized“异常
qq_38472535的博客
08-16 1791
spring boot admin抛出"status":401,"error":"Unauthorized"异常
org.elasticsearch.client.ResponseException: method [POST], host [http://localhost:9200], URI [/note_index/_search?typed_keys=true], status line [HTTP/1.1 503 Service Unavailable] {"error":{"root_cause":[{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"Fr6H_4u1TYisRQKIyLm0Dw","shard":"0","index":"note_index"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"note_index","node":null,"reason":{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"Fr6H_4u1TYisRQKIyLm0Dw","shard":"0","index":"note_index"}}]},"status":503}
05-13
### Elasticsearch 503 错误分析 当遇到 `no_shard_available_action_exception` 或者 `search_phase_execution_exception` 的错误提示时，通常意味着某些分片未能正常工作或者完全不可用。这种情况下，即使 ...
第十阶段【Elasticsearch基础及运维】05：Prometheus监控ElasticSearch以及通过Grafana展示
weixin_40612128的博客
05-06 82
Prometheus监控ElasticSearch以及通过Grafana展示
Elasticsearch运维经验总结
焦振清
12-10 2万+
版本说明：5.6.4（要严格注意ES及其插件、第三方工具的版本匹配关系） 系统负载：（日志集群，日均写入10TB，保留7天） 1，出于高可用的考虑，同一个分区的多个副本不会被分配到同一台机器 如下截图所示，Index：queries，设置20副本，5分片。这个集群当前有14个可用数据节点，queries的0分区在这14个数据节点上均有且仅有一个副本，剩余​​的7个副本显示UNASSIGN...
ecw2c理解元数据：使用BigQuery k-means将4,000个堆栈溢出标签聚类
热门推荐
cunehu1722的博客
07-24 6万+
您如何将超过4,000个活动的Stack Overflow标签分组为有意义的组？ 对于无监督学习和k均值聚类来说，这是一项完美的任务-现在您可以在BigQuery中完成所有这些工作。 让我们找出方法。 Visualizing a universe of clustered tags. Felipe Hoffais a Developer Advocate fo...
Spring boot：访问rest controller 返回 "status": 401, Unauthorized
lianghyan的专栏
01-03 5318
在pom.xml中配置了 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-security</artifactId> </depende...
SpringBoot项目，访问任意接口提示Unauthorized，返回401，并跳转到登陆页面的错误
IntialJ的博客
11-25 4233
地址栏里的login也是在我输入了自己的接口之后，自动跳转到了login 于是用Postman测试，得到401响应： 当时一脸蒙蔽，心想我代码里面没有写拦截器啊，而且拦截之后的页面也不是我写的。刚开始认为可能和端口有关，后来发现不是。于是想着很有可能是SpringBoot自己默认的拦截。网上找了各种资料，果然，发现项目的pom.xml中多了spring-boot-starter-security...
SpringBoot 401 Unauthorized问题
qq_39323945的博客
02-22 2627
当我们使用了Spring-security 之后，Spring Security默认对所有路径进行权限认证，并且提供默认的登陆页面。如果系统最终没有使用到Spring Security，将该依赖移除即可解决问题；
[链接]elasticsearch的服务器响应异常及应对策略
多皮哦的博客
12-13 265
一个写得很好的elasticsearch常见异常的应对方法 https://www.cnblogs.com/jiu0821/p/6075833.html#_label0_7
【项目实战】常见的HTTP状态码（401 - Unauthorized）
本本本添哥
11-24 2万+
400 Bad Request是一种HTTP状态码。400 Bad Request" 是一个常见的HTTP错误代码400 Bad Request是在打开网页时，服务器返回到客户端的一种状态码。400 Bad Request显示在客户端的，也就是400页面。
Elasticsearch出现401异常？业务并没有受到影响？
qq_33999844的博客
06-29 2315
401表示鉴权失败，正常情况下，鉴权失败表示用户名密码信息异常。但是某些场景下，ES 的 Gateway中收到了401的响应，但是业务很正常...
SpringBoot 401 Unauthorized问题解决方案
最爱吃大米的博客
07-20 2万+
SpringBoot 401 Unauthorized问题 使用浏览器访问接口，自动跳转到的页面 @Api("用户信息管理") @RestController @RequestMapping("/test") public class TestController extends BaseController { private final static Map<Integer, UserEntity> users = new LinkedHashMap<Integer, User
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值