You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "John Plevyak (JIRA)" <ji...@apache.org> on 2009/12/17 17:53:18 UTC
[jira] Created: (TS-93) permit do_io_write after open_read to
enable atomic overwrite of an existing object
permit do_io_write after open_read to enable atomic overwrite of an existing object
-----------------------------------------------------------------------------------
Key: TS-93
URL: https://issues.apache.org/jira/browse/TS-93
Project: Traffic Server
Issue Type: Improvement
Components: Cache
Reporter: John Plevyak
Assignee: John Plevyak
Some protocols require atomic overwriting of cache objects. This feature would
permit do_io_write after open_read to enable atomic replacement of the
object the do_io_write could fail if the object is already being written. This would
also require clustering support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TS-93) permit do_io_write after open_read to
enable atomic overwrite of an existing object
Posted by "John Plevyak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Plevyak resolved TS-93.
----------------------------
Resolution: Not A Problem
Fix Version/s: 2.1.0
One can use Cache::open_write with the overwrite flag set, check the header and then either commit or abort the write
to atomically replace an object.
> permit do_io_write after open_read to enable atomic overwrite of an existing object
> -----------------------------------------------------------------------------------
>
> Key: TS-93
> URL: https://issues.apache.org/jira/browse/TS-93
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: John Plevyak
> Assignee: John Plevyak
> Fix For: 2.1.0
>
>
> Some protocols require atomic overwriting of cache objects. This feature would
> permit do_io_write after open_read to enable atomic replacement of the
> object the do_io_write could fail if the object is already being written. This would
> also require clustering support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.