[
https://issues.apache.org/jira/browse/QPID-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270051#comment-17270051
]
ASF GitHub Bot commented on QPID-8500:
--------------------------------------
Dedeepya-T opened a new pull request #77:
URL: https://github.com/apache/qpid-broker-j/pull/77
A context variable is added into BDB HA to give an option to disable
coalescing committer thread. For backward compatibility, by default it will be
set to false.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> [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
>
>
> 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]
