Ankush Kumar created OAK-1709:
---------------------------------
Summary: Diff cache entry too large
Key: OAK-1709
URL: https://issues.apache.org/jira/browse/OAK-1709
Project: Jackrabbit Oak
Issue Type: Bug
Components: upgrade
Affects Versions: 0.20.0
Reporter: Ankush Kumar
Priority: Minor
Following error can be seen while upgrading from CRX2 repo to OAK (Mongo)
07.04.2014 10:00:01.349 *WARN* [FelixStartLevel]
org.apache.jackrabbit.oak.plugins.document.MongoDiffCache Write back of diff
cache entry failed
com.mongodb.MongoInternalException: DBObject of size 26956363 is over Max BSON
size 16777216
at com.mongodb.OutMessage.putObject(OutMessage.java:291)
at com.mongodb.DBApiLayer$MyCollection.insert(DBApiLayer.java:239)
at com.mongodb.DBApiLayer$MyCollection.insert(DBApiLayer.java:204)
at com.mongodb.DBCollection.insert(DBCollection.java:148)
at com.mongodb.DBCollection.insert(DBCollection.java:91)
at
org.apache.jackrabbit.oak.plugins.document.MongoDiffCache$1.done(MongoDiffCache.java:156)
at
org.apache.jackrabbit.oak.plugins.document.Commit.applyToCache(Commit.java:607)
at
org.apache.jackrabbit.oak.plugins.document.CommitQueue.done(CommitQueue.java:80)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.done(DocumentNodeStore.java:520)
Mails regarding this
Hi,
> Could you open an Oak issue (subject for example "Diff cache entry too
> large", at https://issues.apache.org/jira/browse/OAK) with this stack
> trace please? I'm not sure how serious this is, given that it's only a
> warning. But it should be fixed in Oak.
it is not a serious issue. it simply means a diff cache entry will not be
persisted to the capped "changes" collection in mongo. Oak will simply
calculate the diff if an entry in that collection is missing or had been
overwritten.
nothing to worry about, but it would be good to have an issue to avoid the
warning in the first place.
regards
marcel
--
This message was sent by Atlassian JIRA
(v6.2#6252)