[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091801#comment-14091801 ] ASF subversion and git services commented on TS-2362: - Commit d6bcd2d90e0bd7494a14375a45a413974158676f in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=d6bcd2d ] TS-2362: Cache backwards compatibility to 3.2.0. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.1.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091821#comment-14091821 ] Alan M. Carroll commented on TS-2362: - Final result - This change requires no configuration, it should just work. That is, if you install a version with this change then your old cache should be maintained. This applies back to version 3.2.0 - and upgrade from that or later version should preserve the cache. Note that any cache updates are written in the current format, not the old format. Over time this should cause a cache to be updated to the newest version. Because this is now tracked per object, the cost of backwards compatibility should diminish over time as new objects are updated and the compatibility logic can easily detect that to be the case. I incorporated the TS-2564. Previously this fix had been left on the 4.2.X branch because (since 5.0 had a different cache version) it wasn't needed. However, as this enables using 4.2.X caches of all formats we must be able to do that fix up as well. Again, as per above, while the fixup will be done on all objects, new/updatd objects will skip the fixup because the object being permanently fixed is now trivial to detect. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.1.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091632#comment-14091632 ] Alan M. Carroll commented on TS-2362: - Updated patch. Should work for all caches from 3.2.0 to 5.1. In addition to the backwards compatibility, per object version data was added to provide easier forward compatibility in the future. The cache version was bumped but that should not cause loss of cache because it's now backwards compatible! The basic fragment / doc type was changed so that prior formats (without per object version data) are easily distinguished without the cost of format guessing heuristics. The latter are used only when the stripe is indicated to be a back version. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.1.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082381#comment-14082381 ] Alan M. Carroll commented on TS-2362: - Updated patch for master. Testing locally. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.1.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002072#comment-14002072 ] Bryan Call commented on TS-2362: [~amc] Per our discussion at LinkedIn this will be in the 5.1.0 release. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.1.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978425#comment-13978425 ] James Peach commented on TS-2362: - This patch needs to be broken up in to digestible pieces. I suggest starting with the addition diagnostic logging; then add the CryptoHash refactoring and finally the compatibility handling. I think it's also worth spending time on regression tests, given the trouble we have had in this area :-/ Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Labels: Review Fix For: 5.0.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13901881#comment-13901881 ] Alan M. Carroll commented on TS-2362: - I have an alpha version of the patch. It needs some more work but it is a big enough patch and far enough along to need some feedback. In addition to backwards compatibility, it also does some clean up with the URL hashing logic, due to TS-1925. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Fix For: 5.0.0 Attachments: ts-2362.diff Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (TS-2362) Backwards cache compatibility for 4.X (read 3.2)
[ https://issues.apache.org/jira/browse/TS-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840948#comment-13840948 ] Leif Hedstrom commented on TS-2362: --- Marking this for v4.2.0 for now. Backwards cache compatibility for 4.X (read 3.2) Key: TS-2362 URL: https://issues.apache.org/jira/browse/TS-2362 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Alan M. Carroll Assignee: Alan M. Carroll Fix For: 4.2.0 Enable the 4.X series to be able to read 3.2 caches. -- This message was sent by Atlassian JIRA (v6.1#6144)
