Skip to content

This Scrapy project uses Redis and Kafka to create a distributed on demand scraping cluster.

License

Notifications You must be signed in to change notification settings

zookeeperss/scrapy-cluster

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

42 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Scrapy Cluster

This Scrapy project uses Redis and Kafka to create a distributed on demand scraping cluster.

The goal is to distribute seed URLs among many waiting spider instances, whose requests are coordinated via Redis. Any other crawls those trigger, as a result of frontier expansion or depth traversal, will also be distributed among all workers in the cluster.

The input to the system is a set of Kafka topics and the output is a set of Kafka topics. Raw HTML and assets are crawled interactively, spidered, and output to the log. For easy local development, you can also disable the Kafka portions and work with the spider entirely via Redis, although this is not recommended due to the serialization of the crawl requests.

Dependencies

Please see requirements.txt for Pip package dependencies across the different sub projects.

Other important components required to run the cluster

Core Concepts

This project tries to bring together a bunch of new concepts to Scrapy and large scale distributed crawling in general. Some bullet points include:

  • The spiders are dynamic and on demand, meaning that they allow the arbitrary collection of any web page that is submitted to the scraping cluster
  • Scale Scrapy instances across a single machine or multiple machines
  • Coordinate and prioritize their scraping effort for desired sites
  • Persist across scraping jobs or have multiple scraping jobs going at the same time
  • Allows for unparalleled access into the information about your scraping job, what is upcoming, and how the sites are ranked
  • Allows you to arbitrarily add/remove/scale your scrapers from the pool without loss of data or downtime
  • Utilizes Apache Kafka as a data bus for any application to interact with the scraping cluster (submit jobs, get info, stop jobs, view results)

Documentation

Please check out our official Scrapy Cluster documentation for more details on how everything works!

Branches

The master branch of this repository contains the latest stable release code for Scrapy Cluster 1.0.

The dev branch contains bleeding edge code and is currently working towards Scrapy Cluster 1.1. Please note that not everything is documented, finished, tested, or finalized but we are happy to help guide those who are interested.

About

This Scrapy project uses Redis and Kafka to create a distributed on demand scraping cluster.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 55.0%
  • HTML 45.0%