Page Comparison

Highlights in 7.1

Current Snapshot: 

https://sbforge.org/nexus/service/local/artifact/maven/redirect?r=snapshots&g=org.netarchivesuite&a=distribution&v=7.1-SNAPSHOT&e=zip

https://sbforge.org/nexus/service/local/artifact/maven/redirect?r=snapshots&g=org.netarchivesuite&a=heritrix3-bundler&v=7.1-SNAPSHOT&e=zip

1. Fixed (after many years) 

   Jira Legacy
   server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 81c76265-cab2-3ba5-b74d-ee7cd9a2765e key NAS-2870

    whereby all generated revisit-records had badly formatted WARC-Payload-Digest fields and were therefore invalid according to the Warc standard. 
2. Added 3 new link extractors (from the British Library) to heritrix :

   • org.archive.modules.extractor.ExtractorRobotsTxt

   • org.archive.modules.extractor.ExtractorSitemap
   • org.archive.modules.extractor.ExtractorJson 
     Note that ExtractorSitemap deviates slightly in functionality from the British Library version in that it is considerably more lenient in both what it identifies as a sitemap and what Urls it accepts in sitemaps.
3. Added caching of crawl logs when hadoop is used for processing
4. Added caching of metadata-file indexes when hadoop is used for processing
5. Added retry functionality to improve the robustness of the WarcRecordClient
6. Fixed a bug whereby files uploaded from a harvester were not being deleted when the Bitmagasin backend is in use

7. Added retry-handling to Bitmagasin uploads via two new settings keys under settings.common.arcrepositoryClient.bitrepository

   Code Block
   <store_retries>3</store_retries> <retryWaitSeconds>1800</retryWaitSeconds>

   
   

8. Added parameters to manage memory and core usage in hadoop mapper-only jobs 

   Code Block
   settings.common.hadoop.mapred.mapMemoryMb settings.common.hadoop.mapred.mapMemoryCores

   
   

9. Added support for uberized jobs optimised for small tasks in hadoop vis

   Code Block
   settings.common.hadoop.mapred.enableUbertask

   
   

10. Added hdfs caching functionality to hadoop jobs. When this feature is enabled, any local files passed as input to the hadoop job are first copied into hdfs and cached for future use. This should create savings when the same file is processed multiple times, as is often the case for metadata files. This functionality is controlled by the following parameters 

    Code Block
    settings.common.hadoop.mapred.hdfsCacheEnabled settings.common.hadoop.mapred.hdfsCacheDir settings.common.hadoop.mapred.hdfsCacheDays

    
    

11. Improved the performance of the GUI functionality associated with the button "Browse only relevant crawl-log lines for this domain".

The new caching functionality for crawl logs and metadata indexes stores data in a directory specified by the setting

settings.common.webinterface.metadata_cache_dir

 whose default value is "metadata_cache" (relative to the current working directory where the GUIApplication is started). At present there is no automatic cleaning of this directory.

Highlights in 7.0

NetarchiveSuite 7.0 introduces an entirely new backend storage and mass-processing implementation based on software from bitrepository.org and hadoop. The new functionality is enabled by defining the following key in the settings file for all applications: 

<settings>
   <common>
      <arcrepositoryClient>
         <class>dk.netarkivet.archive.arcrepository.distribute.BitmagArcRepositoryClient</class>   

and additionally 

<settings>
   <common>
      <useBitmagHadoopBackend>true</useBitmagHadoopBackend>

The older arcrepositoryClient implementation dk.netarkivet.archive.arcrepository.distribute.JMSArcRepositoryClient will be deprecated in future releases. (The developers are unaware of any other organisations currently using the older client, but please contact us if you still rely on it.)

The new architecture introduces many new keys and external configuration files. There is therefore a separate Guide To Configuring the NetarchiveSuite 7.0 Backend.

Upgrading From Previous NetarchiveSuite Releases

For those using either JMSArcRepositoryClient or LocalArcRepositoryClient there should be no special requirements to upgrade.

Issues Resolved in Release 7.0