You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "hanxq (Jira)" <ji...@apache.org> on 2021/08/03 09:32:00 UTC

[jira] [Commented] (QPID-8500) [Broker-J] Introduce a switch to disable coalescing committer in BDB HA message store

    [ https://issues.apache.org/jira/browse/QPID-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392195#comment-17392195 ] 

hanxq commented on QPID-8500:
-----------------------------

Hi Alex:
 
I tried the solution and found it useless. Are there any followings?
Looking forward to your reply .

> [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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org