Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Channel
    • Labels:
      None

      Description

      The current implementation of derby based JDBC channel uses a single table for storing events. When subject to excessive load all the DML operations happening on this table will lead to lock contention and escalation, thereby impacting the performance of the system.

      It is preferable that the events be distributed over multiple tables so that the overall contention for DML is reduced.

        Activity

        Arvind Prabhakar made changes -
        Field Original Value New Value
        Component/s Channel [ 12316614 ]
        Arvind Prabhakar created issue -

          People

          • Assignee:
            Arvind Prabhakar
            Reporter:
            Arvind Prabhakar
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development