Hi all, we have a clustered production system with 4 nodes that are syncing every 2 seconds. We are using DB Journaling using a central MSSQL Database.
We see that after a single day the local revision id reaches 434339. At this rate of growth in a relative little time this field will reach its highest value and, according to the source, after that jackrabbit will throw an exception because it can't increment the field anymore. Is there a way to reset this counter (perhaps stopping every node of the cluster) to prevent this possible problem? BR Luca Tagliani -- View this message in context: http://jackrabbit.510166.n4.nabble.com/Clustering-local-revision-id-getting-very-high-tp4655731.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
