You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "lin (Jira)" <ji...@apache.org> on 2021/12/01 12:24:00 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lin updated OAK-9629:
---------------------
    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?

If I directly delete some old line from property ":childOrder" , many old channels will can't query out.

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

 

!image-2021-12-01-20-02-14-239.png!

  was:
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?

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

 

!image-2021-12-01-20-02-14-239.png!


> how to solve 10334(BSONObjectTooLarge) error and convert existed node data
> --------------------------------------------------------------------------
>
>                 Key: OAK-9629
>                 URL: https://issues.apache.org/jira/browse/OAK-9629
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>    Affects Versions: 1.24.0
>            Reporter: lin
>            Priority: Blocker
>         Attachments: image-2021-12-01-20-02-14-239.png
>
>
> 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?
> If I directly delete some old line from property ":childOrder" , many old channels will can't query out.
> For more background, please refer to OAK-9620. [https://issues.apache.org/jira/projects/OAK/issues/OAK-9620]
>  
> !image-2021-12-01-20-02-14-239.png!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)