You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2011/01/25 01:48:46 UTC

[jira] Updated: (TS-444) Should we eliminate the partition feature as it is ?

     [ https://issues.apache.org/jira/browse/TS-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-444:
-----------------------------

    Fix Version/s:     (was: 2.1.6)
                   2.1.7

Moving out some non-critical bugs to v2.1.7.

> Should we eliminate the partition feature as it is ?
> ----------------------------------------------------
>
>                 Key: TS-444
>                 URL: https://issues.apache.org/jira/browse/TS-444
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cleanup
>            Reporter: Leif Hedstrom
>             Fix For: 2.1.7
>
>
> Right now, the partition.config configuration / feature allows to allocate cache size for "http" and "mixt". However, MIXT is not supported / needed any more, and with that gone, do we really need the partition.config feature at all? My suggestion would be to remove it, and if it becomes necessary later, add appropriate APIs to manage "partitioning" of the cache via plugin APIs.
> John Plevyak: Thoughts?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.