My Oracle Support Banner

How to remove high IO overhead on clustersync directory? (Doc ID 1507674.1)

Last updated on DECEMBER 07, 2018

Applies to:

Oracle WebCenter Sites - Version 6.3.0 to 7.6.2 [Release FatWire]
Information in this document applies to any platform.

Goal

Why does ContentServer access clustersync files such as {clustersync}/myclustercsdatasourcecategory, {clustersync}/myclusterelementcatalog, etc?
It's causing a performance overhead, as it's accessing the file system each time a query is performed.

The following kind of messages can be found in the logs if accessing the files takes more than 500ms.

[2014-03-31 07:07:00.681][CS.SYNC][WARN] Setting state for {ft.sync}{data source}{tablename} took 3459 ms !!!

Is there any way to disable this behaviour?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 See also:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.