Directory ApacheDS
  1. Directory ApacheDS
  2. DIRSERVER-1321

Clarify relationship between partition.syncOnWrite and apacheDS.syncPeriodMillis configuration attributes

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.4
    • Fix Version/s: 2.0.0-M11
    • Component/s: core
    • Labels:
      None

      Description

      Right now a partition can be configured to sync to disk on each write operation. This is a per partition configuration parameter. Then there is this system wide syncPeriodMillis parameter which can be set to sync up all the partitions on some interval specified. When 0 no sync requests to the core are made.

      The question is does this system wide parameter bypass per partition syncOnWrite settings?

      This solution really stinks because the configuration is spread across two parts of the server and the correlation is hard to grasp because of this. Eventually we need to centralize the schedular service (Quartz) to have each partition register for cyclic triggers that allow it to sync up writes periodically if that is preferred. Otherwise it syncs when each write occurs. We can thus get ride of this syncOnWrite attribute for partitions and just have a syncMillis parameter. If set to 0 then syncs occur on each write. If set to some interval then writes to disk will be cached.

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        Postponed

        Show
        Emmanuel Lecharny added a comment - Postponed
        Hide
        Emmanuel Lecharny added a comment -

        Right now, the SyncOnWrite is associated with the DirectoryService. However, it does not make sense for partitins whih does not cache anything, like the InMemoryPartition or the (yet to come) Oracle partition.

        IMO, this is very partition dependent. So it should be configured in each partition.

        Show
        Emmanuel Lecharny added a comment - Right now, the SyncOnWrite is associated with the DirectoryService. However, it does not make sense for partitins whih does not cache anything, like the InMemoryPartition or the (yet to come) Oracle partition. IMO, this is very partition dependent. So it should be configured in each partition.
        Hide
        Emmanuel Lecharny added a comment -

        Moved back to 2.0.0-RC1

        Show
        Emmanuel Lecharny added a comment - Moved back to 2.0.0-RC1
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Version 2.0.0-M1 has been released.
        Moving all related non-resolved issues to the next version.

        Show
        Pierre-Arnaud Marcelot added a comment - Version 2.0.0-M1 has been released. Moving all related non-resolved issues to the next version.
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Version 2.0.0-M3 has been released a couple months ago.

        Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).

        Show
        Pierre-Arnaud Marcelot added a comment - Version 2.0.0-M3 has been released a couple months ago. Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).
        Hide
        Emmanuel Lecharny added a comment -

        We don't use anymore the SyncWorker, thus the syncMillis parameter is not used anymore.

        Show
        Emmanuel Lecharny added a comment - We don't use anymore the SyncWorker, thus the syncMillis parameter is not used anymore.

          People

          • Assignee:
            Unassigned
            Reporter:
            Alex Karasulu
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development