In our environment, we have two nodes in a cluster with Content services runnin on both the cluster nodes.
One of the process, which is configured to have watched folder end point. This process reads the document from watched folder and stores the same
in specified content space structure. When it is stored in content space we store the node id of the same for future reference.
Now we have run into a situation where content from watched folder is read by Cluster Node A and stored it in Content Space under content services
running on Cluster Node A. Now say after 5 mins we need to retrieve the same content but this time the process to read the content from content space runs on Node B.
Content is read using retrieveContent service by passing node id which we have stored earlier but some reason it is not able to find the content.
Does Livecycle automatically synchronises the cluster nodes for content and how often does it happen?
Any suggestion on how to get around this issue.
For content services in cluster, content is stored at a shared location which can be accessed by each node. Only indexes for this content is synchronized across cluster nodes. Please make sure that content storage root directory is a shared and accessible location for all nodes in the cluster.
Could you please perform a quick test?
1. Go to http://node1:port/contentspace and add a content here.
2. Now go to http://node2:port/contentspace and verify that you can see the content added.
Europe, Middle East and Africa