Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.9.0
-
None
-
cent server/sles client
-
9223372036854775807
Description
listed as minor but when a user does this, we start to get phone calls form other users and then page POC to identify code/user. Workaround is to terminate user job(s).
Oleg has said that Lustre has an existing feature for a client to acquire open lock but off by default. This to mimic NFS behavior.
Ideal change would be that we can specify a number of times that a file is opened on single client at which time lock is acquired. (e.g. 10th time)
Use case is naive user who loop in this way on like 5000+ threads in java:
do until till the sun turns black()
{ fd = open(*my_thread_ID, O_APPEND) calculate_something_small_but_useful() write(fd, *fortytwo, 42) close(fd }Users often don't have complete control over the code they run and as a result may not be able to quickly make even simple changes.
Attachments
Issue Links
- is duplicated by
-
LU-5426 Add more controls for open file cache
- Resolved
- is related to
-
LU-12262 Improve sbi_flags checking
- Resolved
-
LU-14694 racer timeouts with LU-10948
- Resolved
-
LU-14743 Interop: sanity test 429 fails with 'multiop failed'
- Resolved
-
LU-16463 llapi_open_by_fid open should not be cached systematically
- Resolved
-
LU-7915 investigate heuristics for SPARK client getting MDS openlock
- Open
-
LU-10957 Return more lock bits from MDS for open-create
- Open
-
LU-11623 Allow caching of open-created dentries
- Reopened
- is related to
-
LU-4398 mdt_object_open_lock() may not flush conflicting handles
- Resolved
-
LU-10269 Fixes for selective trybits
- Resolved
-
LU-11199 mdsrate open() performance degradation
- Resolved
-
LU-7915 investigate heuristics for SPARK client getting MDS openlock
- Open
-
LU-8585 All Lustre test suites should pass with subdirectory mount
- Open
-
LU-10955 Cancel open lock as part of close request
- Open