Boards migration - add NODES_PAGE_SIZE

Author: andylwelch

docs/assets/boards/cp/boards-cp.yaml

@@ -107,6 +107,7 @@ migration:
     # PROCESSING_LOG_EVERY: 50
     # FIELDS_PAGE_SIZE: 3
     # FIELDS_LOG_EVERY: 50
+    # NODES_PAGE_SIZE: 50
     # IMMEDIATELY_PROCESS_ALL: "false"
     # COMPLETE_ACTIVITY_AFTER_MIGRATED: "false"
     # CREATE_LINK_IN_ACTIVITY_AFTER_MIGRATED: "false"

docs/assets/config/kubernetes/boards.yaml

@@ -152,6 +152,7 @@ migration:
     # PROCESSING_LOG_EVERY: 50
     # FIELDS_PAGE_SIZE: 3
     # FIELDS_LOG_EVERY: 50
+    # NODES_PAGE_SIZE: 50
     # IMMEDIATELY_PROCESS_ALL: "false"
     # COMPLETE_ACTIVITY_AFTER_MIGRATED: "false"
     # CREATE_LINK_IN_ACTIVITY_AFTER_MIGRATED: "false"

docs/boards/troubleshooting/activity-migration.md

@@ -137,8 +137,12 @@ If the Memory issues persist, you can also reduce the amount of concurrent data
 ```yaml
 migration:
   env:
+    # number of activities to process simultaneously (keep low)
     PROCESSING_PAGE_SIZE: 1
+    # number of fields in an activity to process (file attachments, etc)
     FIELDS_PAGE_SIZE: 1
+    # number of items (tasks/entries/comments)  in each activity to process simultaneously
+    NODES_PAGE_SIZE: 50
 ```
 
 Once these values are set you need to deploy the chart again to make them take effect.