Details

    • Type: Sub-task
    • Status: Reopened
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Bigdata Federation
    • Labels:
      None

      Description

      The transaction service is responsible for assigning commit times and tracking "read locks", which are simply the timestamp of outstanding historical read transactions. Data services coordinate with the transaction service to determine when they can release local resources based on the retention age of resources configured on the transaction service and the earliest read locks outstanding on the transaction service.

      Failover for the transaction service is mainly concerned with ensuring that the failover transaction server assign commit times not less than those assigned by the current leader. The transaction server also maintains an index over the historical commit times.

      Replication can be easily achieved using HDFS.

        Attachments

          Activity

            People

            Assignee:
            bryanthompson bryanthompson
            Reporter:
            bryanthompson bryanthompson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: