Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 426
    • Issues 426
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #2027
Closed
Open
Issue created Mar 16, 2021 by Mark OLESEN@markMaintainer

reading processor dirs can hang

As noted by @Chiara in EP1528, processes can hang on startup.

Running with timeStampMaster with non-distributed case directories, but with case directories that contain different portions of the processorNN structure. Eg,

node0:
/scratch/job10/constant, /scratch/job10/system, /scratch/processor{0,1,2,3}

node1:
/scratch/job10/constant, /scratch/job10/system, /scratch/processor{4,5,6,7}
...

The startup optimization logic added in #1946 (closed) results in a false listing since the directory information is scattered from node0, which only has processors (0-3). Proposed fix is to place the optimization onto a switch, and restore the previous behaviour of polling on all nodes by default.

Edited Mar 17, 2021 by Mark OLESEN
Assignee
Assign to
Time tracking