You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Eric Balsa (JIRA)" <ji...@apache.org> on 2011/06/20 23:10:47 UTC
[jira] [Created] (TS-846) Remap processor options could be
integrated to a single option
Remap processor options could be integrated to a single option
--------------------------------------------------------------
Key: TS-846
URL: https://issues.apache.org/jira/browse/TS-846
Project: Traffic Server
Issue Type: Improvement
Components: Configuration
Affects Versions: 3.0.0
Reporter: Eric Balsa
Assignee: Eric Balsa
Priority: Minor
Fix For: 3.1.0
TS_ReadConfigInteger(use_separate_thread, "proxy.config.remap.use_remap_processor");
and
TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
should be changed to a single config
TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
whereby a setting of "0" would indicate not to use a separate thread(s) for remapping.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-846) Remap processor options could be
integrated to a single option
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-846:
-----------------------------
Fix Version/s: (was: 3.1.1)
3.3.0
> Remap processor options could be integrated to a single option
> --------------------------------------------------------------
>
> Key: TS-846
> URL: https://issues.apache.org/jira/browse/TS-846
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 3.0.0
> Reporter: Eric Balsa
> Assignee: Eric Balsa
> Priority: Minor
> Fix For: 3.3.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> TS_ReadConfigInteger(use_separate_thread, "proxy.config.remap.use_remap_processor");
> and
> TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
> should be changed to a single config
> TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
> whereby a setting of "0" would indicate not to use a separate thread(s) for remapping.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-846) Remap processor options could be
integrated to a single option
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-846:
-----------------------------
Fix Version/s: (was: 3.1.0)
3.1.1
Moving out some bugs to 3.1.1, please rearrange if you plan on fixing any of these in the next few weeks.
> Remap processor options could be integrated to a single option
> --------------------------------------------------------------
>
> Key: TS-846
> URL: https://issues.apache.org/jira/browse/TS-846
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 3.0.0
> Reporter: Eric Balsa
> Assignee: Eric Balsa
> Priority: Minor
> Fix For: 3.1.1
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> TS_ReadConfigInteger(use_separate_thread, "proxy.config.remap.use_remap_processor");
> and
> TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
> should be changed to a single config
> TS_ReadConfigInteger(num_remap_threads, "proxy.config.remap.num_remap_threads");
> whereby a setting of "0" would indicate not to use a separate thread(s) for remapping.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira