[NUTCH-2910] FetchItemQueues overloaded constructor also interprets fetcher timeout as -1 e.g. no-timeout.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.18
• Fix Version/s: 1.19
• Component/s: fetcher
• Assignee: Lewis John McGibbney
• Reporter: Lewis John McGibbney
• Created: 28/Nov/21 01:37
• Updated: 13/Mar/24 14:51
• Resolved: 02/Dec/21 01:46

Description

The FetchItemQueues overloaded constructor attempts to obtain the NON-EXISTENT fetcher.timelimit configuration property.

this.timelimit = conf.getLong("fetcher.timelimit", -1);

As you can see a default value of -1 is provided. The first parameter is however wrong. It should instead reference the following configuration property.

<property>
  <name>fetcher.timelimit.mins</name>
  <value>-1</value>
  <description>This is the number of minutes allocated to the fetching.
  Once this value is reached, any remaining entry from the input URL list is skipped 
  and all active queues are emptied. The default value of -1 deactivates the time limit.
  </description>
</property>

Note, fetcher.timelimit.mins

I think that this essentially means the Fetcher has no time limit which is ofcourse not desired.