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 2010/12/07 06:55:10 UTC

[jira] Resolved: (TS-570) SplitDNS schedules on wrong thread when "dns_threads > 0"

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

Leif Hedstrom resolved TS-570.
------------------------------

    Resolution: Fixed

> SplitDNS schedules on wrong thread when "dns_threads > 0"
> ---------------------------------------------------------
>
>                 Key: TS-570
>                 URL: https://issues.apache.org/jira/browse/TS-570
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: DNS
>    Affects Versions: 2.1.5
>         Environment: 2.1.5 trunk
>            Reporter: qianshi
>            Assignee: Leif Hedstrom
>            Priority: Minor
>             Fix For: 2.1.5
>
>         Attachments: TS-570.diff, TS-570.patch
>
>
> In main() function, SplitDNSConfig::startup() is called before dnsProcessor.start() like 1. 
> In SplitDNSConfig::startup(), reconfigure() schedule threads like 2. 
> In dnsProcessor.start(), create threads for dns and split dns like 3.
> So when split dns is enable and dns threads more than 0, split dns uses no the dns threads which created to do so but 0 thread, that may be not the initial purpose of creating the dedicated threads for dns and split dns.
> 1.
>     SplitDNSConfig::startup();
>     dnsProcessor.start();
> 2.
>   EThread *thread = eventProcessor.eventthread[ET_DNS][0];
>   thread->schedule_imm(dnsH, ET_DNS);
> 3.
>   ET_DNS = eventProcessor.spawn_event_threads(dns_threads);

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