You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/08/15 16:43:45 UTC

[jira] [Resolved] (CONNECTORS-1227) Queue processing for an added job does not seem to prioritize a second job's documents right

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

Karl Wright resolved CONNECTORS-1227.
-------------------------------------
    Resolution: Not A Problem

I verified that this effect is caused by document prioritization, and the system is behaving as designed.  Starting a job when another is running causes documents from that job to be queued up right at the point that the running job's documents are being queued.  This makes it slow to get a job going when another is running, but is not actually a bug.

> Queue processing for an added job does not seem to prioritize a second job's documents right
> --------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1227
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1227
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 2.1
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Minor
>             Fix For: ManifoldCF 1.10, ManifoldCF 2.2
>
>
> Start a job.  Immediately start a second job.  You should see the second job begin to process documents after the first job makes it as far through the queue to get to documents that the second job added.  But the second job still does not process documents at that point.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)