directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSERVER-1321) Clarify relationship between partition.syncOnWrite and apacheDS.syncPeriodMillis configuration attributes
Date Wed, 04 Mar 2009 15:39:56 GMT
Clarify relationship between partition.syncOnWrite and apacheDS.syncPeriodMillis configuration
attributes 
----------------------------------------------------------------------------------------------------------

                 Key: DIRSERVER-1321
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1321
             Project: Directory ApacheDS
          Issue Type: Improvement
          Components: core
    Affects Versions: 1.5.4
            Reporter: Alex Karasulu


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message