<Workspace name="crx.default" simpleLocking="true">
<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager">
<param name="autoOptimizeAt" value="01:00-02:00" />
</PersistenceManager>
Under: <Workspace name="${wsp.name}" simpleLocking="true">
<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager">
<param name="autoOptimizeAt" value="01:00-02:00" />
</PersistenceManager>
<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager">
<param name="autoOptimizeAt" value="01:00-02:00" />
</PersistenceManager>
And finally:
<Cluster>
<Journal class="com.day.crx.persistence.tar.TarJournal">
<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager">
<param name="autoOptimizeAt" value="01:00-02:00" />
</PersistenceManager>
</Journal>
</Cluster>
Solved! Go to Solution.
this? http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#Journal
On the same page, this is good stuff too: http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#TarPersistenceManager
scott
I have the same issue. The following parameters does not mention when to schedule tarJournal opt, ie the "autoOptimizeAt" flage is missing for tarJournal. How can I schedule tarJournal opt
<
Cluster
syncDelay
=
"5000"
>
<
Journal
class
=
"com.day.crx.persistence.tar.TarJournal"
>
<
param
name
=
"sharedPath"
value
=
"/cq/crx-quickstart/repository/shared"
/>
<
param
name
=
"maximumSize"
value
=
"104857600"
/>
<
param
name
=
"maximumAge"
value
=
""
/>
<
param
name
=
"maximumFiles"
value
=
"0"
/>
<
param
name
=
"portList"
value
=
""
/>
<
param
name
=
"bindAddress"
value
=
""
/>
<
param
name
=
"connectTimeout"
value
=
"2000"
/>
<
param
name
=
"socketTimeout"
value
=
"60000"
/>
<
param
name
=
"operationTimeout"
value
=
"30000"
/>
<
param
name
=
"becomeMasterOnTimeout"
value
=
"false"
/>
</
Journal
>
</
Cluster
>
Views
Replies
Total Likes
this? http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#Journal
On the same page, this is good stuff too: http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#TarPersistenceManager
scott
None of the links provided mentions anything about when to schedule tarJournal. Can you let me know if its possible to schedule tarJournal opt, if yes how can I do that.
Views
Replies
Total Likes
Hi,
See this section: http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#Configuring%20the%20T... for the following config element, and the autoOptimizeAt attribute:
<PersistenceManager class="com.day.crx.persistence.tar.TarPersistenceManager"> <param name="maxFileSize" value="256"/> <param name="autoOptimizeAt" value="2:00-5:00"/> <param name="bindAddress" value=""/> <param name="portList" value=""/> <param name="lockClass" value="com.day.crx.util.NativeFileLock"/> <param name="lockTimeout" value="0"/> <param name="fileMode" value="rw"/> <param name="optimizeSleep" value="1"/> <param name="maxIndexBuffer" value="32"/> </PersistenceManager>
scott
Views
Replies
Total Likes
I don't think you can configure a separate maintenance window for the optimization of the Tar Journal.
For the "crx.default" workspace, and the "version" workspace you can.
Views
Replies
Total Likes
JayanKandathil wrote...
I don't think you can configure a separate maintenance window for the optimization of the Tar Journal.
For the "crx.default" workspace, and the "version" workspace you can.
I would like the answer to this as well. If you set the "autoOptimizeAt" parameter in repository.xml and workspace.xml everyplace you can, you will see tarJournal optimization still run from 2AM-5AM. Can anyone confirm or deny if this can be changed?
Views
Replies
Total Likes
Views
Likes
Replies