Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OAK MERGE ERROR when saving the history to "/var/statistics/achistory" for really large AC setups #145

Closed
ghenzler opened this issue Jan 30, 2017 · 1 comment
Closed

OAK MERGE ERROR when saving the history to "/var/statistics/achistory" for really large AC setups #145

ghenzler opened this issue Jan 30, 2017 · 1 comment
Assignees
@ghenzler
Milestone
1.9.2

Comments

@ghenzler
Copy link
Member

It turns out that for large installations the following error can occur:

26.01.2017 10:48:53.349 *ERROR* [qtp1594121387-23585-ACTool-Config-Worker] biz.netcentric.cq.tools.actool.installationhistory.impl.AcHistoryServiceImpl RepositoryException: javax.jcr.InvalidItemStateException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 107976 ms)
...
Caused by: org.apache.jackrabbit.oak.api.CommitFailedException: OakMerge0001: OakMerge0001: Failed to merge changes to the underlying store (retries 5, 107976 ms)
...
Caused by: org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: DBObject of size 16962907 is over Max BSON size 16777216
...
Caused by: com.mongodb.MongoInternalException: DBObject of size 16962907 is over Max BSON size 16777216

Either we should save as binary or choose to split across multiple properties (the first option probably being the better)

@jochenkoschorke FYI
@mtstv mtstv mentioned this issue Feb 6, 2017
Closed
@ghenzler ghenzler mentioned this issue Feb 6, 2017
Merged
@ghenzler ghenzler assigned ghenzler and unassigned jochenkoschorke Feb 6, 2017
ghenzler added a commit that referenced this issue Feb 6, 2017
@ghenzler
#145 just use non-verbose history for if verbose history becomes too
61a24f4 
large
@ghenzler ghenzler added this to the v1.9.2 milestone Feb 6, 2017
@ghenzler
Copy link
Member Author

ghenzler commented Feb 6, 2017

Fixed by using the non-verbose log to write the property if the text becomes too big.

@ghenzler ghenzler closed this as completed Feb 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ghenzler ghenzler

Labels
None yet
Projects
None yet
Milestone
1.9.2
Development

No branches or pull requests
2 participants
@ghenzler @jochenkoschorke