Cassandra报错: com.datastax.driver.core.ConnectionException:Pool was closed during initialization

最新推荐文章于 2025-11-28 02:11:49 发布
原创 最新推荐文章于 2025-11-28 02:11:49 发布 · 2.4k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#cassandra #Pool was closed during initial

当遇到com.datastax.driver.core.ConnectionException: Pool was closed during initialization的警告时，虽然这是一个Exception，但实际上它属于WARN级别，不会影响Cassandra的正常运行。此问题可能与节点配置或重复因子设置不当有关，但实践中表明可以忽略此警告。

 

Cassandra报错: com.datastax.driver.core.ConnectionException:Pool was closed during initialization

2019-01-26 16:19:46,223|WARN|cluster1-nio-worker-3|com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
poc-216|-1|32301|OcgAux-1-0|Error creating pool to /192.168.14.212:9042
com.datastax.driver.core.ConnectionException: [/192.168.14.212:9042] Pool was closed during initialization
        at com.datastax.driver.core.HostConnectionPool$2.onSuccess(HostConnectionPool.java:147)
        at com.datastax.driver.core.HostConnectionPool$2.onSuccess(HostConnectionPool.java:133)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:145)
        at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:185)
        at com.google.common.util.concurrent.Futures$CombinedFuture.setOneValue(Futures.java:1764)
        at com.google.common.util.concurrent.Futures$CombinedFuture.access$400(Futures.java:1608)
        at com.google.common.util.concurrent.Futures$CombinedFuture$2.run(Futures.java:1686)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:145)
        at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:185)
        at com.google.common.util.concurrent.Futures$FallbackFuture$1$1.onSuccess(Futures.java:479)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
        at com.google.common.util.concurrent.Futures$ImmediateFuture.addListener(Futures.java:106)
        at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
        at com.google.common.util.concurrent.Futures$FallbackFuture$1.onFailure(Futures.java:476)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:145)
        at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:202)
        at com.google.common.util.concurrent.Futures$FallbackFuture$1$1.onFailure(Futures.java:487)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
        at com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
        at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
        at com.google.common.util.concurrent.Futures$FallbackFuture$1.onFailure(Futures.java:476)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:145)
        at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:202)
        at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:902)
        at com.google.common.util.concurrent.Futures$1$1.run(Futures.java:635)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
        at com.google.common.util.concurrent.Futures$1.run(Futures.java:632)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
        at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
        at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:145)
        at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:202)
        at com.google.common.util.concurrent.SettableFuture.setException(SettableFuture.java:68)
        at com.datastax.driver.core.Connection$1.operationComplete(Connection.java:161)
        at com.datastax.driver.core.Connection$1.operationComplete(Connection.java:144)
        at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:514)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:507)
        at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:486)
        at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:427)
        at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:129)
        at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.fulfillConnectPromise(AbstractEpollStreamChannel.java:864)
        at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.finishConnect(AbstractEpollStreamChannel.java:883)
        at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollOutReady(AbstractEpollStreamChannel.java:900)
        at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:376)
        at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:302)
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)
        at java.lang.Thread.run(Thread.java:745)

首先不要被这个错误吓到，这虽然是一个Excepiton，但它的提示是WARN级别，经过博主实际使用证明，并不影响cassandra的正常使用。

估计可能是节点和重复因子的配置不合理引起的。既然完全不影响使用，就可以不理会。End.

 

Zoe_Wong
关注
Cassandra 自定义重试策略
qq_42076214的博客
01-06 816
在 Apache Cassandra 中，自定义重试策略的主要目的是为了应对各种运行时异常，如读超时、写超时、节点不可用、请求中止和响应错误等。这些异常示例包括 CassandraUncategorizedException 和 WriteTimeoutException。通过实现自定义重试策略，如 DatastaxCustomRetry 类，可以在遇到特定异常时提供更精细的重试逻辑。这个类包含了不同场景下的重试决策，例如读超时、写超时和节点不可用。在 Cassandra 配置类 CassandraConf
cassandra节点启动报错：java.io.UTFDataFormatException
zhang546030919的博客
12-26 737
"java.io.UTFDataFormatException: malformed input around byte 0"错误是由于Cassandra尝试读取保存的缓存文件时发生了UTF格式异常。在提供的错误消息中，缓存目录为：/home/data0/cassandra/cassandra_caches/saved_caches/。请注意，删除缓存文件将导致Cassandra重新生成缓存数据。cassandra数据量500G，重新生成缓存用了10分钟。Cassandra将自动重新创建缓存文件。
Cassandra连接报错com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for que
weixin_43482279的博客
09-09 1601
Cassandra连接报错
【亲测免费】 探索DataStax Java驱动器：连接Cassandra数据库的新维度
最新发布
gitblog_00011的博客
11-28 482
在大数据领域，Apache Cassandra是一个广受欢迎的分布式NoSQL数据库系统，以其高可扩展性和容错性著称。为了充分利用Cassandra的强大功能，开发人员需要强大的客户端驱动器。这就是DataStax Java驱动器进入视野的地方。本文将深入探讨这个项目的特性、技术实现以及如何利用它进行高效的数据操作。 ## 项目简介 DataStax Java驱动器是一个开源的Java库，允许
cassandra连接报错：tried：localhost 127 0 0 1：9042
u011250186的博客
04-07 1621
com datastax driver core exceptions NoHostAvailableException: All host(s) tried for query failed (tried: localhost 127 0 0 1:9042 (com datastax driver core exceptions InvalidQueryException: unconfigu...
Cassandra Java Driver Reference 4.11
freeRoad
04-24 420
文档入口： https://docs.datastax.com/en/developer/java-driver/4.11/ 1 Session Build import com.datastax.oss.driver.api.core.CqlSession; import com.datastax.oss.driver.api.core.cql.*; try (CqlSession session = CqlSession.builder().build()) { ...
在对Cassandra数据库执行post方法时，报错如下 com.datastax.oss.driver.api.core.servererrors.InvalidQueryException: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING at com.datastax.oss.driver.api.core.servererrors.InvalidQueryException.copy(InvalidQueryException.java:48) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.util.concurrent.CompletableFutures.getUninterruptibly(CompletableFutures.java:149) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.cql.CqlPrepareSyncProcessor.process(CqlPrepareSyncProcessor.java:59) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.cql.CqlPrepareSyncProcessor.process(CqlPrepareSyncProcessor.java:31) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.session.DefaultSession.execute(DefaultSession.java:230) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.api.core.cql.SyncCqlSession.prepare(SyncCqlSession.java:224) ~[java-driver-core-4.14.1.jar:na]
08-30
logging.level.com.datastax.oss.driver.core=DEBUG logging.level.org.springframework.data.cassandra=DEBUG 重新设计数据模型建议： - 根据查询需求设计表：Cassandra鼓励为每个查询设计专门的表（反范式化...
在这个Cassandra表插入数据时，idea报错如下，如何解决： com.datastax.oss.driver.api.core.servererrors.InvalidQueryException: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING at com.datastax.oss.driver.api.core.servererrors.InvalidQueryException.copy(InvalidQueryException.java:48) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.util.concurrent.CompletableFutures.getUninterruptibly(CompletableFutures.java:149) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.cql.CqlPrepareSyncProcessor.process(CqlPrepareSyncProcessor.java:59) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.cql.CqlPrepareSyncProcessor.process(CqlPrepareSyncProcessor.java:31) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.internal.core.session.DefaultSession.execute(DefaultSession.java:230) ~[java-driver-core-4.14.1.jar:na] at com.datastax.oss.driver.api.core.cql.SyncCqlSession.prepare(SyncCqlSession.java:224) ~[java-driver-core-4.14.1.jar:na] 对应的代码如下所示： @Override public UserRegistryResultDTO registry(UserRegistryDTO registryDTO) { UserRegistryResultDTO result = new UserRegistryResultDTO(); // Cassandra 验证逻辑 validateRegistryInfo(registryDTO, result); if (result.getStatus() != RegistryStatusEnum.FAILED) { try { CassandraUser newUser = dtoToUser(registryDTO); // 使用 insert 而不是 save 避免更新操作 cassandraOperations.insert(newUser); result.setStatus(RegistryStatusEnum.SUCCESS); result.setMessage("Registration successful in Cassandra"); } catch (Exception e) { log.error("Cassandra insert error", e); result.setStatus(RegistryStatusEnum.FAILED); result.setMessage("Database error"); } } return result; }
08-30
### Cassandra 插入操作报错解决方案 #### 错误根源分析 该错误发生在插入数据时，但核心问题与**数据模型设计**和**查询逻辑**相关： 1. **插入前的隐式查询**：`validateRegistryInfo()` 方法可能包含未优化的...
看看这个报错 Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: pet-cassandra-cebu-tapocare-use1-002.base-service.svc.cluster.local/10.50.242.0:9042 (com.datastax.driver.core.exceptions.TransportException: [pet-cassandra-cebu-tapocare-use1-002.base-service.svc.cluster.local/10.50.242.0:9042] Connection has been closed), pet-cassandra-cebu-tapocare-use1-003.base-service.svc.cluster.local/10.50.245.243:9042 (com.datastax.driver.core.exceptions.TransportException: [pet-cassandra-cebu-tapocare-use1-003.base-service.svc.cluster.local/10.50.245.243:9042] Connection has been closed), pet-cassandra-cebu-tapocare-use1-001.base-service.svc.cluster.local/10.50.240.237:9042 (com.datastax.driver.core.exceptions.TransportException: [pet-cassandra-cebu-tapocare-use1-001.base-service.svc.cluster.local/10.50.240.237:9042] Connection has been closed))
11-18
这个错误表明您的应用无法连接到Cassandra数据库集群，所有尝试连接的节点都失败了。以下是详细分析和解决方案： --- ### **错误原因分析** 1. **网络连通性问题**（最常见） - 应用Pod与Cassandra服务之间的网络...
Datastax Java Driver驱动所需JAR包
01-16
Datastax Java Driver驱动所需JAR包
cassandra java jar_Cassandra数据库Java驱动Datastax Java Driver使用手册1-数据库连接
weixin_34561824的博客
03-05 589
package com.cassandra;import com.datastax.driver.core.Cluster;import com.datastax.driver.core.ResultSet;import com.datastax.driver.core.Row;import com.datastax.driver.core.Session;public class Connect...
datastax 数据库在使用过程不稳定
linuxarmsummary的专栏
03-01 1089
window 调试环境、com.datastax.driver.core.exceptions.NoHostAvailableException:1，删除掉问题日志 2，cmd 命令进入 apache-cassandra\bin>cassandra 记录（待以后解决）
cassandra java cql,使用DataStax Java驱动程序1.0.4使用CQL连接到Cassandra时出现异常
weixin_36328527的博客
02-23 339
I have Cassandra 1.2.11 running on my laptop. I can connect to it using nodetool and cqlsh but when I try and use the DataStax 1.0.4 Java API to connect using CQL 3.0 I get the following error:com.dat...
Cassandra-Springboot 异常问题总结
qq_36389344的博客
07-06 2574
最近在做一个Springboot-Cassandra相关项目，由于本人是新接触Cassandra，所以遇到很多棘手的问题，耗费了大量时间查找资料定位问题等，现将期间遇到的一些棘手问题罗列，以便日后复盘学习。 文中将使用到的表定义 CREATE TYPE cass_stdy.address ( addr text, mail text ); CREATE TABLE cass_stdy.user ( id uuid PRIMARY KEY, addr li...
Cassandra2.0以后的新API类和接口总结
qq838642798的博客
02-17 1632
总的来说，cassandra新增了一个包，名字：com.datastax.driver.core 这个包提供了很多api类和接口，让在代码中对cassandra数据库的操作变得更容易和更简洁了。 首先从创建一个连接说起 1． com.datastax.driver.core.PoolingOptions连接池类 PoolingOptions pools = new PoolingOptio
程序包xxx不存在解决办法
m0_67677436的博客
03-06 3924
记录一下今天在工作中遇到的程序包xxx不存在的解决办法
HikariPool-1 - Exception during pool initialization.的解决方法
热门推荐
LYly_B的博客
04-13 2万+
HikariPool-1 - Exception during pool initialization.的解决方法。 HikariPool-1-池初始化期间出现异常。 1.在application.properties中的spring.datasource.url后增加一个&useSSL=false&serverTimezone=UTC。 #配置数据源 spring.datas...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值