Bug 432565
Summary: | # rhmd --store-async <yes|no> options | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Lana Brindley <lbrindle> |
Component: | Messaging_Installation_and_Configuration_Guide | Assignee: | Lana Brindley <lbrindle> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Kim van der Riet <kim.vdriet> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | beta | CC: | gsim, jonathan.robie, mhideo |
Target Milestone: | --- | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-18 01:47:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lana Brindley
2008-02-12 21:41:56 UTC
There are two ways to achieve persistence: 1. The journal, which uses asynchronous IO (AIO for short) - hence the name async. 2. The BDB database, which is somewhat slower, and synchronous. It is true that the default is now to use the journal. I also think it is confusing to refer to the BDB database as "a persistence journal". Perhaps this should be reworded to: If yes (or 1), the broker will use an asynchronous journal for message persistence; if no (or 0), the broker will use synchronous storage. Defaults to yes (asynchronous). Document now reads: <row> <entry> <command>--store-async <yes|no></command> </entry> <entry> If <command>yes</command> (or <command>1</command>), the broker will use an asynchronous journal for message persistence; if <command>no</command> (or <command>0</command>), the broker will use synchronous storage. Defaults to <command>yes</command> (asynchronous). </entry> </row> |