Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #15719

Closed
Open
Opened Apr 17, 2015 by Arturo Filasto@art

Handle scaling issues with OONI pipeline

It looks like the new machine I acquired for hosting the OONI pipeline just 6 months ago has now run out of disk space.

585G	mongodb
68G	pipeline

It appears that since we have started compressing the reports now the majority of the disk usage is sucked up by mongodb.

I think this is a good opportunity to consider the migration over to elasticsearch as was suggested by @robertkeizer: https://github.com/TheTorProject/ooni-pipeline/commit/c20ad24e96736eb8dbebda6b23fe6ccde944b066#commitcomment-10450852

Support for elastic search in ooni-pipeline has been implemented inside of https://github.com/TheTorProject/ooni-pipeline/compare/feature/elasticsearch.

Once that is merged we need to consider the possibility of starting building an elastic search cluster for all the data.

I propose we use this venue to discuss.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#15719