Shared Journal-fileJournal pros and cons? | Community
Skip to main content
purnendraSingh
Adobe Employee
purnendraSinghAdobe Employee
Adobe Employee
October 16, 2015
Solved

Shared Journal-fileJournal pros and cons?

  • October 16, 2015
  • 2 replies
  • 759 views

I just came across one client  where they are using “shard all “(Shared Data Store and shared Journal-fileJournal) configuration. I have never come across such configuration till now.

I am looking to know pros and cons of using this configuration. Is there any known  issue related to performance with this configuration.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Here is some more infromation from one of our Adobe Product members:

"The main reason to use the shared journal is reduce and maybe eliminate the split-brain problem.  I have come across issues in the past with things like code deploys that restart the CRX OSGi bundles that can cause the repo to loose its mind.  While these issues are rare the customer always wants a fool-proof setup and process so sometimes we have to resort to the shared journal.  The downside to a shared journal is that you are doing a lot of network file I/O so a very low latency network FS is required or performance will suffer."

See:

http://www.day.com/content/kb/home/Crx/Troubleshooting/JournalTooMuchDiskSpace.html
 

http://archive.dev.day.com/discussion-groups/content/lists/adobe-dev/2013-08/2013-08-30_CQ_shared_Tar_Journal_cluster__who_is_using_this__Gardner_Buchanan.html?q=CQ%20shared%20Tar%20Journal%20cluster

http://dev.day.com/docs/en/crx/current/administering/cluster.html#Shared External Database


 

2 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

Here is some more infromation from one of our Adobe Product members:

"The main reason to use the shared journal is reduce and maybe eliminate the split-brain problem.  I have come across issues in the past with things like code deploys that restart the CRX OSGi bundles that can cause the repo to loose its mind.  While these issues are rare the customer always wants a fool-proof setup and process so sometimes we have to resort to the shared journal.  The downside to a shared journal is that you are doing a lot of network file I/O so a very low latency network FS is required or performance will suffer."

See:

http://www.day.com/content/kb/home/Crx/Troubleshooting/JournalTooMuchDiskSpace.html
 

http://archive.dev.day.com/discussion-groups/content/lists/adobe-dev/2013-08/2013-08-30_CQ_shared_Tar_Journal_cluster__who_is_using_this__Gardner_Buchanan.html?q=CQ%20shared%20Tar%20Journal%20cluster

http://dev.day.com/docs/en/crx/current/administering/cluster.html#Shared External Database


 

purnendraSingh
Adobe Employee
purnendraSinghAdobe EmployeeAuthor
Adobe Employee
October 16, 2015

thanks for your reply 

Do you think having Journal fileJornal  between two clustered node(NFS network attached storage) is safe or it is not having any major impact on performance ?

Terms & ConditionsAccessibility statement

Loading footer...