Mongodb CRUD成功,但在播放中出现最后一个错误。反应Mongo 2.3.8
已经成功地使用play(2.3.8)Responsive Scala示例代码连接并从mongo实例创建/读取,但无法摆脱LastError,它困扰着我,因为我最初错误配置了主机名。启用调试:logger.reactivemongo=DEBUG显示详细信息:Mongodb CRUD成功,但在播放中出现最后一个错误。反应Mongo 2.3.8,mongodb,play-reactivemongo,Mongodb,Play Reactivemongo,已经成功地使用play(2.3.8)Responsive Scala示例代码连接并从mongo实例创建/读取,但无法摆脱LastError,它困扰着我,因为我最初错误配置了主机名。启用调试:logger.reactivemongo=DEBUG显示详细信息: [debug] r.c.a.MongoDBSystem - received a checked write request [debug] r.api.Failover - Got an
[debug] r.c.a.MongoDBSystem - received a checked write request
[debug] r.api.Failover - Got an error, retrying... (try #1 is scheduled in 500 ms)
reactivemongo.core.actors.Exceptions$PrimaryUnavailableException$: MongoError['No primary node is available!']
at reactivemongo.core.actors.Exceptions$PrimaryUnavailableException$.<clinit>(actors.scala) ~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
at reactivemongo.core.actors.MongoDBSystem$$anonfun$pickChannel$4.apply(actors.scala:508) ~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
at reactivemongo.core.actors.MongoDBSystem$$anonfun$pickChannel$4.apply(actors.scala:508) ~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
at scala.Option.getOrElse(Option.scala:120) ~[scala-library-2.11.4.jar:na]
at reactivemongo.core.actors.MongoDBSystem.pickChannel(actors.scala:508) ~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
[debug] r.c.a.MongoDBSystem - ConnectAll Job running... Status: Node[wengen:27017: Unknown (1/10 available connections), latency=0], auth=Set()
[debug] r.c.a.MongoDBSystem - ConnectAll Job running... Status: Node[wengen:27017: Unknown (1/10 available connections), latency=0], auth=Set()
[debug] r.c.a.MongoDBSystem - ConnectAll Job running... Status: Node[wengen:27017: Unknown (1/10 available connections), latency=0], auth=Set()
[debug] r.c.a.MongoDBSystem - ConnectAll Job running... Status: Node[wengen:27017: Unknown (1/10 available connections), latency=0], auth=Set()
[info] r.c.a.MongoDBSystem - The node set is now available
[info] r.c.a.MongoDBSystem - The primary is now available
[debug] r.c.a.MonitorActor - set: a primary is available
and the insert of the POST is fine but for this lastError:
[debug] r.c.a.MongoDBSystem - Sending request expecting response Request(3001,0,Insert(0,playdb.newpersons),BufferSequence(DynamicChannelBuffer(ridx=0, widx=60, cap=64),WrappedArray()),reactivemongo.api.ReadPreference$Primary$@47979aa3,None) by connection Connection([id: 0xedfcbc47, /192.168.15.46:55680 => wengen/192.168.15.67:27017],Connected,Set(),None) of node wengen:27017
[debug] r.c.a.MongoDBSystem - Got a response from -302203833! Will give back message=Response(MessageHeader(110,45,3001,1),Reply(8,0,0,1),LittleEndianHeapChannelBuffer(ridx=36, widx=110, cap=110),ResponseInfo(-302203833)) to promise scala.concurrent.impl.Promise$DefaultPromise@bd0cdcc
[debug] r.c.a.MongoDBSystem - {3001} it's a getlasterror
[debug] application - Successfully inserted with LastError: reactivemongo.core.commands.LastError: DatabaseException['empty lastError message']
[debug]r.c.a.MongoDBSystem-收到已检查的写入请求
[debug]r.api.Failover-出现错误,正在重试。。。(try#1计划在500毫秒内完成)
reactivemongo.core.actors.Exceptions$PrimaryUnavailableException$:MongoError['没有可用的主节点!']
在reactivemongo.core.actors.Exceptions$PrimaryUnavailableException$(actors.scala)~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
在reactivemongo.core.actors.MongoDBSystem$$anonfun$pickChannel$4.apply(actors.scala:508)~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
在reactivemongo.core.actors.MongoDBSystem$$anonfun$pickChannel$4.apply(actors.scala:508)~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
在scala.Option.getOrElse(Option.scala:120)~[scala-library-2.11.4.jar:na]
在reactivemongo.core.actors.MongoDBSystem.pickChannel(actors.scala:508)~[reactivemongo_2.11-0.10.5.0.akka23.jar:0.10.5.0.akka23]
[调试]r.c.a.MongoDBSystem-连接所有正在运行的作业。。。状态:节点[wengen:27017:未知(1/10可用连接),延迟=0],身份验证=设置()
[调试]r.c.a.MongoDBSystem-连接所有正在运行的作业。。。状态:节点[wengen:27017:未知(1/10可用连接),延迟=0],身份验证=设置()
[调试]r.c.a.MongoDBSystem-连接所有正在运行的作业。。。状态:节点[wengen:27017:未知(1/10可用连接),延迟=0],身份验证=设置()
[调试]r.c.a.MongoDBSystem-连接所有正在运行的作业。。。状态:节点[wengen:27017:未知(1/10可用连接),延迟=0],身份验证=设置()
[信息]r.c.a.MongoDBSystem-节点集现在可用
[信息]r.c.a.MongoDBSystem-主系统现在可用
[调试]r.c.a.MonitorActor-设置:主控制器可用
插入帖子也可以,但最后一个错误是:
[debug]r.c.a.MongoDBSystem-通过连接([id:0xedfcbc47,/192.168.15.46:55680=>wengen/192.168.15.67:27017])发送期望响应请求的请求(3001,0,Insert(0,playdb.newpersons),BufferSequence(DynamicChannelBuffer(ridx=0,widx=60,cap=64),wrappeddarray()),reactivemongo.api.ReadPreference$Primary$@47979aa3,None)(),无)节点文根:27017
[调试]r.c.a.MongoDBSystem-从-302203833获得响应!将返回message=response(MessageHeader(110,453001,1),Reply(8,0,0,1),LittleEndianHeapChannelBuffer(ridx=36,widx=110,cap=110),ResponseInfo(-302203833))承诺scala.concurrent.impl.promise$DefaultPromise@bd0cdcc
[debug]r.c.a.MongoDBSystem-{3001}这是一个getlasterror
[调试]应用程序-已成功插入LastError:reactivemongo.core.commands.LastError:DatabaseException['empty LastError message']
mongo中的db.resetError()
无法消除此问题。插入已从集合中确认。代码如下:
有什么建议吗?如
[debug]
和[info]
前缀所示,它们不是错误
这是ReactiveMongo驱动程序在管理连接池和复制集时的详细日志记录
可以将日志记录级别设置为警告
,以抑制此类消息
如
[debug]
和[info]
前缀所示,它们不是错误
这是ReactiveMongo驱动程序在管理连接池和复制集时的详细日志记录
可以将日志记录级别设置为警告
,以抑制此类消息
如
[debug]
和[info]
前缀所示,它们不是错误
这是ReactiveMongo驱动程序在管理连接池和复制集时的详细日志记录
可以将日志记录级别设置为警告
,以抑制此类消息
如
[debug]
和[info]
前缀所示,它们不是错误
这是ReactiveMongo驱动程序在管理连接池和复制集时的详细日志记录
可以将日志记录级别设置为警告
,以抑制此类消息
在
logback
中覆盖:
<logger name="reactivemongo.api.Failover2">
<level value="INFO"/>
</logger>
<logger name="reactivemongo.core.actors">
<level value="INFO"/>
</logger>
这将仅使的
reactivemongo的滥用调试消息静音
在logback中覆盖
:
<logger name="reactivemongo.api.Failover2">
<level value="INFO"/>
</logger>
<logger name="reactivemongo.core.actors">
<level value="INFO"/>
</logger>
这将仅使的
reactivemongo的滥用调试消息静音
在logback中覆盖
:
<logger name="reactivemongo.api.Failover2">
<level value="INFO"/>
</logger>
<logger name="reactivemongo.core.actors">
<level value="INFO"/>
</logger>
这将仅使的
reactivemongo的滥用调试消息静音
在logback中覆盖
:
<logger name="reactivemongo.api.Failover2">
<level value="INFO"/>
</logger>
<logger name="reactivemongo.core.actors">
<level value="INFO"/>
</logger>
这将仅使的滥用调试消息静音
reactivemongo
这是一个正确的答案-从根本上说,reactivemongo应该低于