Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 738
    • Issues 738
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 200
    • Merge requests 200
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #17892

Closed (moved)
(moved)
Open
Created May 12, 2020 by Boonthanome Nouanesengsy@boonthDeveloper

AggregateDataSet filter runs into MPI size constraint

There have been occasions where an mpi error is encountered where mpi is trying to send a message that is too large. The error looks like "This operation not yet supported for more than bytes".

This error was last encountered with the AggregateDataSet filter, in which Bob Kares was going from 30K procs to 200 procs. I've also encountered this error in the past, too. Bob has got it working now, but I'm not sure what he is doing differently.

@patchett2002 @cory.quammen @utkarsh.ayachit

Assignee
Assign to
Time tracking