lmammino/distributed-jwt-cracker

Ability to monitor clients and reassign their ongoing batches in case of failure

Open

#3 opened on Oct 1, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (7 forks)github user discovery
enhancementhacktoberfesthelp wanted

Repository metrics

Stars
 (60 stars)
PR merge metrics
 (PR metrics pending)

Description

This requires to introduce a mechanism to monitor the clients (e.g. ping or timeout) and to store in the server state a queue of batches waiting for recovery. When a new batch is requested by a client then the next batch is provided from the recovery queue. Only if the recovery queue is empty the cursor can be moved forward and a new batch can be distributed to a client.

Contributor guide

Research direction
Implement a heartbeat mechanism for clients and a recovery queue in the server state. When a client fails, add its incomplete batches to the recovery queue. On new batch requests, serve from recovery queue first.
Tech stack
javascriptnodejs
Domain
backenddistributed systems
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60