gpt4 book ai didi

java - 为什么 Riak 将 "inavailable channel closed"消息记录为 ERROR

转载 作者:塔克拉玛干 更新时间:2023-11-02 19:59:42 24 4
gpt4 key购买 nike

我不是 Riak 专家,但看起来 inavailable channel closed 消息应该是 INFO 级别,而不是 ERROR 级别的日志消息。当我们的服务器启动以获取用户数据时,我们打开一些 Riak 连接,然后它们超时(这应该没问题,对吧?),当它们超时时显示 inavailable channel closed 消息。

我们是否错误地使用了 Riak?有真正的错误吗?或者这应该只是一个 INFO 级别,因为它是正常 Riak 生命周期的一部分?

http://grepcode.com/file/repo1.maven.org/maven2/com.basho.riak/riak-client/2.0.0/com/basho/riak/client/core/RiakNode.java

13:13:51.533 [nioEventLoopGroup-2-1] DEBUG s.r.s.i.n.u.i.JavassistTypeParameterMatcherGenerator - Generated: scifinder.riak.shaded.io.netty.util.internal.__matchers__.com.basho.riak.client.core.RiakMessageMatcher
13:13:51.541 [nioEventLoopGroup-2-1] DEBUG s.r.s.i.n.u.i.JavassistTypeParameterMatcherGenerator - Generated: scifinder.riak.shaded.io.netty.util.internal.__matchers__.com.basho.riak.client.core.FutureOperationMatcher
13:13:51.552 [main] INFO com.basho.riak.client.core.RiakNode - RiakNode started; riak.address.org:8087
13:13:51.553 [main] INFO c.basho.riak.client.core.RiakCluster - RiakCluster is starting.
13:13:51.865 [main] INFO com.basho.riak.client.core.RiakNode - RiakNode started; riak.address.org:8087
13:13:51.865 [main] INFO c.basho.riak.client.core.RiakCluster - RiakCluster is starting.
13:13:52.174 [main] INFO com.basho.riak.client.core.RiakNode - RiakNode started; riak.address.org:8087
13:13:52.174 [main] INFO c.basho.riak.client.core.RiakCluster - RiakCluster is starting.
13:13:52.206 [main] DEBUG com.basho.riak.client.core.RiakNode - Operation being executed on RiakNode riak.address.org:8087
13:13:52.220 [nioEventLoopGroup-4-1] DEBUG s.r.s.i.n.util.ResourceLeakDetector - -Dscifinder.riak.shaded.io.netty.leakDetectionLevel: simple
13:13:52.233 [nioEventLoopGroup-4-1] DEBUG com.basho.riak.client.core.RiakNode - Operation onSuccess() channel: id:-486690393 riak.address.org:8087
13:13:52.234 [nioEventLoopGroup-4-1] DEBUG c.basho.riak.client.core.RiakCluster - operation complete; remaining retries: 2
13:13:52.235 [nioEventLoopGroup-4-1] DEBUG com.basho.riak.client.core.RiakNode - Channel id:-486690393 returned to pool
13:13:52.235 [nioEventLoopGroup-4-1] DEBUG com.basho.riak.client.core.RiakNode - Released pool permit

错误日志

14:13:31.708 [nioEventLoopGroup-2-1] ERROR com.basho.riak.client.core.RiakNode - inAvailable channel closed; id:601172895 riak.address.org:8087
14:13:32.036 [nioEventLoopGroup-3-1] ERROR com.basho.riak.client.core.RiakNode - inAvailable channel closed; id:-319701844 riak.address.org:8087
14:13:32.410 [nioEventLoopGroup-4-1] ERROR com.basho.riak.client.core.RiakNode - inAvailable channel closed; id:-486690393 riak.address.org:8087

最佳答案

看起来开发人员注意到了同样的事情,因为 this bug去年6月提交,消息在this PR中降为INFO级别一个月后。

如果您仍然将它们视为错误,请将您的 java-riak-client 更新为 v2.0.7或以后。

关于java - 为什么 Riak 将 "inavailable channel closed"消息记录为 ERROR,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/30198905/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com