Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-9629

how to solve 10334(BSONObjectTooLarge) error and convert existed node data

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Invalid
    • 1.24.0
    • None
    • jcr
    • None
    • Important

    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

       

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            linqq lin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment