Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-673

Investigate other object store implementations

    XMLWordPrintable

Details

    • Task
    • Resolution: Obsolete
    • Major
    • None
    • None
    • Transaction Core
    • None

    Description

      "... spin out messaging journal into separate component so we can consume it. Also look at other disk I/O alternatives, basically trying to batch syncs so one is shared by many tx rather than one per tx. Also maybe preliminary investigation of in-memory replication of logs via jgroups."

      See related links. Need to re-check performance of transaction log and maybe make it the default implementation.

      Attachments

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBTM-683 Rework ObjectStore implementations around new interfaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBTM-397 Pull higher-performance transaction log implementation across from backup

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBTM-643 Create 3 interfaces for different aspects of ObjectStore

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBTM-486 Refactor log store

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              nmcl2001 Mark Little
              nmcl2001 Mark Little
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: