Child pages
  • TEST2
Skip to end of metadata
Go to start of metadata
Test snapshot harvesting in detail and subsequent follow-up harvesting   

 

 

Prepare Installation

On devel@kb-prod-udv-001.kb.dk:

export TESTX=TEST2
export PORT=807?
export MAILRECEIVERS=foo@bar.dk
##stop_test.sh
##cleanup_all_test.sh
## Disable deduplication after the installation (in the settings for harvestjobmanager or by using a dedup_disabled H3 template)
##prepare_test.sh deploy_config_dedup_disabled.xml
all_test.sh

Override default_order_xml with default_orderxml_nodedup.xml

Where PORT=807? correspond to the test port allocated in the Setup DK test environment page and MAILRECEIVERS=foo@bar.dk should correspond to your own mail address. 

Check Domain Statistics

Go to the GUI on http://kb-test-adm-001.kb.dk:8074/HarvestDefinition/ (replace port number as needed) and

  1. Check that the installation has initially 16 domains loaded
  2. Check that you can search for domains by name or wildcard
  3. Check that you can create a new domain (add unknown001.dk: it doesn't exist)
  4. Add a new configuration to an existing domain. Use non-default values for Max Hops, Honour robots and Extract Javascript. Confirm that it is listed in the domain definition with the correct attributes. (you might need to click on show unused configurations).

Global Crawler Traps

  1. Download the file crawlertrapsCollection.txt and upload it as a global-crawler-trap list.
  2. Download the list again from the GUI and compare it with original list. If necessary use "sort -u" to remove any duplicates and ensure that the two versions are ordered identically.  A sample Unix command line:  diff <(sort -u crawlertrapsCollection.txt ) <(sort -u crawlertrap ) (note that any empty lines are also removed during upload)

Update Byte Limits

Update the "Maximum number of bytes" for the defaultconfig for six domains as follows:

kb.dk100000
statsbiblioteket.dk100001
netarkivet.dk100002
dbc.dk100003
bs.dk100004
sulnudu.dk100005

Add Alias Domain

  1. Using the GUI, set netarkivet.dk to be an alias of kb.dk.
    1. Go to edit page of the domain 'netarkivet.dk' using the HarvestDefinition/Definitions-find-domains.jsp
    2. In the "Alias of" field, type 'kb.dk'
    3. Click 'save'
  2.  Confirm that it is listed on the "Alias Summary" page.
  3. Now try to make dbc.dk an alias of netarkivet.dk. This should fail because chains of aliases are not allowed.
    1. Go to edit page of the domain 'dbc.dk' using the HarvestDefinition/Definitions-find-domains.jsp
    2. In the "Alias of" field, type 'netarkivet.dk'
    3. Click save. An error message should be shown on screen; 
      "Cannot make domain 'dbc.dk' an alias of 'netarkivet.dk', as that domain is already an alias of 'kb.dk'"

Start a Snapshot Harvest

  1. Create and activate a snapshot harvest with a "Max number of bytes per domain" of 1000000.
  2. Wait until HarvestJobManager on the Status page shows that jobs have been created for the harvest.

Check that Alias Domain is not Harvested

For each job generated, check that netarkivet.dk is not included in the domains harvested.

Check that Jobs Complete as Expected

Use the Harvest Status section of the GUI to monitor the jobs. When all jobs have finished, check each job in turn to see that the domains report their "Stopped due to" as follows:

 
 bs.dk                   Domain Completed
 kum.dk                  Max Bytes limit reached
 oernhoej.dk             Domain Completed
 drive-badmintonklub.dk  Max Bytes limit reached
 sulnudu.dk              Domain-config byte limit reached
 statsbiblioteket.dk     Domain-config byte limit reached
 kb.dk                   Domain-config byte limit reached (currently blocked so Domain Completed)
 raeder.dk               Domain Completed
 trinekc.dk              Max Bytes limit reached
 kaarefc.dk              Domain Completed
 kaareogtrine.dk         Max Bytes limit reached
 dbc.dk                  Domain-config byte limit reached
 unknown001.dk           Domain Completed
 slothchristensen.dk     Max Bytes limit reached
 pligtaflevering.dk      Max Bytes limit reached
 trineogkaare.dk         Max Bytes limit reached
 sy-jonna.dk             Max Bytes limit reached

If any of these have a different reason, investigate to see if the new stop reason makes sense. Generally speaking, domains with DomainCompleted will have significantly under 1000000 bytes harvested, while the other will be somewhat, but not vastly, over this limit.

Add a New Alias

kb is currently blocked so use statsbiblioteket.dk instead

Set sulnudu.dk to be an alias of kb.dk

Change a Byte Limit

For kb.dk set the Maximum Number of Bytes on defaultconfig to -1 (no limit).

Start a Second Phase Snapshot Harvest

Create a new snapshot harvest with a 'Max number of bytes per domain' of 5MB (i.e, 5000000 bytes) , harvesting domains not completed in the previous harvest.

Test NAS Heritrix Integration

In "Harvest status > All Jobs"  wait until one of the jobs has nonzero progress. Click on the Job ID to enter H3 Remote Access.

Pause the job. 

Check the following functionality:

  • Progression/Queues
  • Crawllog: check cache update, filtering, paging
  • Reports: click on at least two of them
  • Show/delete frontier: delete some items from the frontier
  • Add RejectRules: add a new rule
  • Modify budget: add an object limit to some domain or subdomain

Now restart the job. Then immediatiely ...  

Restart The System

  1. Stop NAS with the "stop_test.sh" command and restart it with the "start_test.sh" command. After some time, the job you paused and unpaused should appear in the state "Failed".

     
  2. Restart the job by clicking the "Restart?" button. A new job should be created and the old one should have the status "Resubmitted (Job X)".
  3. Wait for the job to finish.
  4. Meanwhile click on the JobID for the failed job, then click on "Browse reports for jobs".
  5. You should see a list of available reports including one called "scripting_events.log". This is the log of alterations you made to the frontier via H3 Remote Access. Click on it.
  6. Assuming you have the correct viewerproxy setup (See Setup DK test environment) you should a log line describing your action. Something similar to

    2016-02-02T14:05:59.170Z Action from user CSR: Deleted 563 uris matching regex '.*kb.dk.*'

[ This section is commented out because none of the current NAS-H3 scripts override the crawler-bean settings.

Check the Overrides are Applied

For the failed job check that the overrides are visible by looking at the order.xml in the metadata reports:

  1. Setup the viewerproxy as described in Setup DK test environment.
  2. Goto the Job details page for the newly finished job by clicking the link in the JobID column.
  3. Click the Browse reports for jobs link.
  4. Goto the metadata://netarkivet.dk/crawl/setup/order.xml report and confirm the modified settings have been updated in the final version of the order.xml.

]

Check that Alias Domains are not Harvested

For each job generated in the last harvest:

  1. Check that netarkivet.dk and sulnudu.dk are not listed as being harvested.
  2. Check that neither domain appears in the order templates for any of the jobs with the (possible) exception of the following lines:
metadata.operatorContactUrl=http://netarkivet.dk/webcrawler/
metadata.operatorFrom=info@netarkivet.dk

This can be done by grepping with a command like

[devel@kb-prod-udv-001 ~]$ ssh netarkiv@sb-test-bar-001.statsbiblioteket.dk grep netarkivet.dk /netarkiv/0001/TEST2/filedir/*-metadata-1.warc | grep -v 'metadata:'

or by scp'ing the metadata file to kb-prod-udv-001 and inspecting it with "less". (Or just by displaying the order template in the NAS GUI and searching.)

Check Byte Limits for the Second Harvest

  1. Confirm that the stop reason "Max Bytes limit reached" or "Domain Completed" is given for all the domains included.
  2. Confirm that domains for which the domain-config byte limit was reached in the previous harvest are not present in any job in this harvest. (e.g. dbc.dk). The exception to this is the one domain for which you changed the domain limit to unlimited.

[ No longer valid. We now include DeDuplication in TEST2. Check that there was no Deduplication

  1. Goto the Job details page for the newly finished job by clicking the link in the JobID column.
  2. Click the Browse reports for jobs link.
  3. Confirm that there was no DeDuplicator report, eg. verify the string duplicatereductionjob doesn't appear in the listed reports.  ]

Stop the Test and Clean-Up

stop_test.sh

cleanup_all_test.sh

  • No labels