Skip to content

How can I effectively debug BSON DocumentTooLarge errors? #5953

Discussion options

You must be logged in to vote

I guess it helps a lot to write out the problem! It triggered me hunting out the mongo conf, dig around the collections and query for the execution id of the workflow and decoding parts of the document I found (which was 13.2MB itself).

It looks like the workflow document stores all the context inside itself, so I'm going to expect one of the workflows I have is expanding its context too much. I'm currently playing around with the idea of just referencing task outputs rather than storing them in context, and reusing/deleting context keys when i don't need them anymore.

Edit: Referencing the task outputs using task(...) meant these no longer needed to be in the context and so saved on all …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by MatthewStrickland
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant