Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #192

Closed
Open
Opened Jun 06, 2016 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

shared file reduction bug in current modules

Currently, the shared file reduction code for all modules qsorts the array of I/O records to get shared records in a contiguous extent to run the reduction on. The issue is that, if the records are registered in different orders on different processes (e.g., by opening file records in different orders on different processes), each process could have inconsistent ordering of the records. This would cause the reduction to give incorrect results as the reduction would mix file records from different files.

The workaround is to continue sorting s.t. shared records are stored in a contiguous region, but to use the Darshan record identifiers to further sort the shared file region in a deterministic way (i.e., ascending or descending order).

Reported by Glenn Lockwood.

Assignee
Assign to
3.1.0
Milestone
3.1.0
Assign milestone
Time tracking
None
Due date
None
1
Labels
defect
Assign labels
  • View project labels
Reference: darshan/darshan#192