[OAK-9629] how to solve 10334(BSONObjectTooLarge) error and convert existed node data

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Invalid
• Affects Version/s: 1.24.0
• Component/s: jcr
• Flags: Important
• Assignee: Unassigned
• Reporter: lin
• Created: 01/Dec/21 12:20
• Updated: 02/Dec/21 12:37
• Resolved: 02/Dec/21 12:37

Description

Hello,

Could you please help me to solve this issue ASAP? Our QA and staging environments encounter this error "message OakOak0001: Command failed with error 10334 (BSONObjectTooLarge): 'BSONObj size: 16848200 (0x1011548) is invalid. Size must be between 0 and 16793600(16MB) First element: _id: \"1:/channels\""  .

We are very worried about this error will occur in the production environment.

Since we used "nt:unstructured" as JCR primary type of node /channels, and the value of property ":childOrder" is larger, almost 16M .

There are 2092 channels in our db, one line of property ":childOrder" about 800kb.

Could you please tell me how to reduce the existed  property ":childOrder" value, and how to convert existed date from "nt:unstructured" to "oak:unstructured"?  Do you have reference about it?

What will be the impact if I directly delete some old lines from property ":childOrder" ?

For more background, please refer to OAK-9620. https://issues.apache.org/jira/projects/OAK/issues/OAK-9620

 

Issue Links

• duplicates: OAK-9620 Encounter "OakOak0001: Command failed with error 10334(BSONObjectTooLarge)" during stress testing