ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-2841) IGFS: Lock trash during file overwrite only if there is clear evidence of a conflict.
Date Wed, 16 Mar 2016 06:39:33 GMT
Vladimir Ozerov created IGNITE-2841:
---------------------------------------

             Summary: IGFS: Lock trash during file overwrite only if there is clear evidence
of a conflict.
                 Key: IGNITE-2841
                 URL: https://issues.apache.org/jira/browse/IGNITE-2841
             Project: Ignite
          Issue Type: Task
          Components: IGFS
    Affects Versions: 1.5.0.final
            Reporter: Vladimir Ozerov
             Fix For: 1.6


*Problem*
Currently we always lock trash ID during during file create if "overwrite" flag is set to
{{true}}. This is very pessimistic strategy leading to contention on trash. In lots cases
there will be no existing file.

*Solution*
1) Trash should be locked only if there is a clear evidence that old file exists.
2) If we didn't lock trash and found existing file - go to re-try loop. This is very unlikely
case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message