| Summary: | XID Size - 25 or 53 bytes? | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | mdarretta <mdarrett> |
| Component: | Messaging_Programming_Reference | Assignee: | Alison Young <alyoung> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.3 | CC: | gsim, iboverma, kim.vdriet, lbrindle |
| Target Milestone: | 2.0 | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-24 02:55:20 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
mdarretta
2011-01-27 19:01:29 UTC
Please provide further information for documentation. LKB There's nothing else I can provide. Engineering will need to clarify which numbers are correct. Thanks. Gordon, Are you able to help out with source documentation? LKB Kim, can you have a look at the apparent inconsistency in the journal sizing text and comment on corrections needed? I can't find any reference to 25 bytes, but 24 bytes is the size used for local transactions according to the text, I assume this is what you mean in comment #1. Section 6.4.4, paragraph 1 starts with: "When transactions are used, a transaction ID (XID) is added to each record. The size of the XID is 24 bytes for local transactions. For distributed transactions, the user supplies the XID, which is usually obtained from the transaction monitor, and may be any size. ..." In the following sections describing each record type, the transaction is described as: "Transaction ID (XID) size (24 bytes for local transactions, arbitrary size for distributed transactions)" The confusion probably arises from Example 6.2 not explicitly stating that the transactions will be distributed, and are supplied by the user. In this example, the supplied XID is a human-readable UUID format of 53 bytes (as opposed to the local transaction format which is binary and 24 bytes). I suggest the following changes to the text of Example 6.2: Old text: "This example shows how to calculate journal size when transactions are used with a persistent queue. Here are the characteristics of the messaging queue for this example:" New text: "This example shows how to calculate journal size when distributed transactions are used with a persistent queue. The XID will be supplied by the user in this case. Here are the characteristics of the messaging queue for this example:" |