Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.core
beat.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.corebeat.core
  • Issues
  • #68

Closed
Open
Opened Feb 26, 2019 by Samuel GAIST@samuel.gaist
  • Report abuse
  • New issue
Report abuse New issue

Refactor ZMQ architecture

The current architecture works well but connection with the scheduler may get lost after a long period of network inactivity.

The task here is to refactor the architecture so that adding and removing node as well as crashing nodes gets improved handling and thus avoids as much as possible "blocked" experiments.

Assignee
Assign to
ZMQ resilience improvement
Milestone
ZMQ resilience improvement
Assign milestone
Time tracking
None
Due date
None
1
Labels
enhancement
Assign labels
  • View project labels
Reference: beat/beat.core#68