You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/16 18:47:16 UTC

[jira] [Commented] (TS-1728) Need a way to assign storage entries to volumes

    [ https://issues.apache.org/jira/browse/TS-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659693#comment-13659693 ] 

ASF subversion and git services commented on TS-1728:
-----------------------------------------------------

Commit 1d8179df5bfbde4331ee94519c7a7a9d45f2ebe3 in branch refs/heads/issues/TS-1728 from Phil Sorber <so...@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1d8179d ]

TS-1728: Assign storage entries to volumes

Introduces the volume assignment in storage.config, on an optional
basis. No change is needed in the config if you don't want to use
this feature.

* Add an optional reference to the volume number in storage.config,
  and the Span object, in Store.h and Store.cc
* Add the volume reference to DiskVol, CacheProcessor::start_internal
  (in Cache.cc)
* Change cplist_reconfigure (in Cache.cc) to constrain mapping
* Fix bytes_used and percent_used per volume stats

                
> Need a way to assign storage entries to volumes
> -----------------------------------------------
>
>                 Key: TS-1728
>                 URL: https://issues.apache.org/jira/browse/TS-1728
>             Project: Traffic Server
>          Issue Type: Wish
>          Components: Cache
>            Reporter: Jan van Doorn
>            Assignee: Phil Sorber
>            Priority: Minor
>             Fix For: 3.3.3
>
>         Attachments: vol.patch
>
>
> See http://www.knutsel.com/vol/compare/ for a write up and some test results on this. We are proposing a simple way to hard link storage.config entries to volume.config and thus hosting.config entries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira