[
https://issues.apache.org/jira/browse/QPID-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393776#comment-17393776
]
hanxq commented on QPID-8500:
-----------------------------
Hi Alex:
My durability policy is WRITE_NO_SYN,NO_SYN,SIMPLE_MAJORITY. QPID version is
6.1.1， je is 7.4.5, qpid.bdb.ha.disable_coalescing_committer = true . but
other exception occurred.(Failed to dequeue message 1672 in transaction
<Transication id = "8105"> ....)。
---------------
Error message：2021-08-05 15:19:07,041 ERROR [IO-/128.196.18.19:21588
(o.a.q.s.s.b.BDBConfigurationStore) Failed to dequeue message 1672 in
transaction <Transaction id="8405"> 2021-08-05 15:19:07,041 ERROR
[IO-/128.196.18.19:21588 (o.a.q.s.s.b.BDBConfigurationStore) Failed to dequeue
message 1672 in transaction <Transaction id="8405">
com.sleepycat.je.rep.Replicawriteexcepton: (JE 7.4.5) Problem closing
transaction 8405. The current state is:UNKNOWN. The node transitioned to this
state at:Thu Aug 05 15:19:06 CST 2021 at
com.sleepycat.je.rep.txn.ReadonlyTxn.disallowReplicaWrite(ReadonlyTxn.java:114)-[je-7.4.5.jar:7.4.51
at com.sleepycat.je.rep.txn.Readonlylxn.preLogwithoutLock
(ReadonlyTxn.java:102) ~[je-7.4.5.jar:7.4.5】 at
com.sleepycat.je.dbi.cursorImpl.locklN (CursorImp1.java:3561)
~je-1.4.5.jar:7.4.5] at
com.sleepycat.je.dbi.CursorImpl.deletecurrentRecord(CursorImp1.java:900)~[je-7-4.5-jar:7.4.5
at
com.sleepycat.je.Cursor.deleteNoNotify(Cursor.java:2412)~[je-7.4.5.jar:7.4.5]
at com.sleepycat.je.cursor.deleteInternal(Cursor.java:2353)[je-7.4.5.jar:7.4.5]
at com.sleepycat.je.Database.deleteInternal(Database.java:1169)
-[je-7.4.5.jar:7.4.5] at
com.sleepyeat.je.Database.delete(Database.java:1128) -tje-7.4.5.jar:7.4.5] at
com.sleepycat.je.Database.delete(Database.java:1230)-[je-7.4.5.jar:7.4.5] at
org.apache.gpid.server.store.berkeleydb.AbstractBDBMessageStore.dequeueMessage(AbstractBDBMessageStore.java:671)[qpid-babstore-6.1.1.jar:6.1.1]
at
org.apache.apid.server.store.berkeleydb.AbstractBDBMessageStore.accessS1000(AbstractBDBMe3sageStore.java:74)
[cpid-bdbstore-6.1.1.jar:6.1.1 at
ora.apache.apid.server.store.berkeleydb.AbstractBDBMessageStoreSBDBTransaction.dequeueMessage(AbstractBDBM
ssageStore.java:1326)[gpid-bdbstore-6.1.1.jar:6.11] at
org.apache.qpid.server.txn.AsyncAutoCommitTransaction.dequeue
(AsyncAutoCommitTransaction.java:103)[apid-broker-core-6.1.1.iar:6.1.11 at
org.apache.pid.server.protocol.v0 10.serverSession.acknowledge
(ServerSession.java:567)[opid-broker-plugins-amap-0-10-protoco1-6.1.1.iar:6.1.11
> [Broker-J] Introduce a switch to disable coalescing committer in BDB HA
> message store
> -------------------------------------------------------------------------------------
>
> Key: QPID-8500
> URL: https://issues.apache.org/jira/browse/QPID-8500
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.4, qpid-java-broker-7.1.12
>
>
> A BDB JE replication Feeder fails sporadically with errors like the one below
> {noformat}
> Halted log file reading at file 0x7472c8 offset 0x199d07
> offset(decimal)=1678599 prev=0x199cd5:
> entry=DEL_LN_TXtype=31,version=14)
> prev=0x199cd5
> size=44
> Next entry should be at 0x199d49
> com.sleepycat.je.EnvironmentFailureException: (JE 7.4.5) want to read
> 52,431,066,320 but reader at 52,431,066,327 UNEXPECTED_STATE: Unexpected
> internal state, may have side effects.
> at
> com.sleepycat.je.EnvironmentFailureException.unexpectedState(EnvironmentFailureException.java:428)
> at
> com.sleepycat.je.rep.stream.FeederReader.checkForPassingTarget(FeederReader.java:297)
> at
> com.sleepycat.je.rep.stream.FeederReader.isTargetEntry(FeederReader.java:317)
> at
> com.sleepycat.je.log.FileReader.readNextEntryAllowExceptions(FileReader.java:332)
> at com.sleepycat.je.log.FileReader.readNextEntry(FileReader.java:245)
> at
> com.sleepycat.je.rep.stream.FeederReader.scanForwards(FeederReader.java:280)
> at
> com.sleepycat.je.rep.stream.MasterFeederSource.getWireRecord(MasterFeederSource.java:70)
> at
> com.sleepycat.je.rep.impl.node.Feeder$OutputThread.writeAvailableEntries(Feeder.java:1266)
> at
> com.sleepycat.je.rep.impl.node.Feeder$OutputThread.run(Feeder.java:1144)
> {noformat}
> Based on discussion at
> [https://community.oracle.com/tech/developers/discussion/4300421/master-fails-unexpectedly-due-to-feeder-output-halted-log-file-reading-at-file-0x334f63-offset-0x8ce]
> we need a way to configure broker without a coalescing committer. The local
> sync policy would be set as per user virtual host settings.
> A context variable can be added into BDB HA to disable coalescing committer
> thread.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
