You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2009/03/04 16:39:56 UTC
[jira] Created: (DIRSERVER-1321) Clarify relationship between
partition.syncOnWrite and apacheDS.syncPeriodMillis configuration
attributes
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.
[jira] Updated: (DIRSERVER-1321) Clarify relationship between
partition.syncOnWrite and apacheDS.syncPeriodMillis configuration
attributes
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1321:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> 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
> Fix For: 2.0.0-RC1
>
>
> 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.
[jira] Updated: (DIRSERVER-1321) Clarify relationship between
partition.syncOnWrite and apacheDS.syncPeriodMillis configuration
attributes
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1321:
-----------------------------------------
Fix Version/s: 2.0.0
Postponed
> 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
> Fix For: 2.0.0
>
>
> 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.
[jira] Commented: (DIRSERVER-1321) Clarify relationship between
partition.syncOnWrite and apacheDS.syncPeriodMillis configuration
attributes
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719192#action_12719192 ]
Emmanuel Lecharny commented on DIRSERVER-1321:
----------------------------------------------
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.
> 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
> Fix For: 2.0.0
>
>
> 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.