dstrack creates snapshots mainly from the CLI. This could create clashes and incorrect snapshots in the following scenarios:
- Usre launches a snapshot creation, user modified underlying data while snapshot is being computed.
- User launches dstrack across threads or processes.
Potential solution:
Implement file locking, to make threads and processes wait for file to be unlocked before creating a snapshot. The file should only be released by dstrack after a snapshot is created. It should still be possible to give users control of this behavior in case they can ensure that files are not modified during snapshot creation.
dstrack creates snapshots mainly from the CLI. This could create clashes and incorrect snapshots in the following scenarios:
Potential solution:
Implement file locking, to make threads and processes wait for file to be unlocked before creating a snapshot. The file should only be released by dstrack after a snapshot is created. It should still be possible to give users control of this behavior in case they can ensure that files are not modified during snapshot creation.