[
https://issues.apache.org/jira/browse/QPID-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395679#comment-17395679
]
hanxq edited comment on QPID-8500 at 8/19/21, 3:35 AM:
-------------------------------------------------------
Hi Alex:
My durability policy is WRITE_NO_SYN,NO_SYN,SIMPLE_MAJORITY. QPID version is
6.1.1， je is 7.4.5 or 7.0.6, qpid.bdb.ha.disable_coalescing_committer = true
。In the weekend the exception occurred(Halted log file reading at file
0x7472c8 offset 0x199d07 offset(decimal)=1678599 prev=0x199cd5:
entry=DEL_LN_TXtype=31,version=14))。
The solution of QPID-8500 need a higher version ？ Next step，I will use QPID
version is 8.0.5， je is 7.4.5。
------------------------
Today，I use QPID version is 8.0.5 ，je is 7.4.5 , But the exception still exsit。
was (Author: [email protected]):
Hi Alex:
My durability policy is WRITE_NO_SYN,NO_SYN,SIMPLE_MAJORITY. QPID version is
6.1.1， je is 7.4.5 or 7.0.6, qpid.bdb.ha.disable_coalescing_committer = true
。In the weekend the exception occurred(Halted log file reading at file
0x7472c8 offset 0x199d07 offset(decimal)=1678599 prev=0x199cd5:
entry=DEL_LN_TXtype=31,version=14))。
The solution of QPID-8500 need a higher version ？ Next step，I will use QPID
version is 8.0.5， je is 7.4.5。
> [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]
