Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Genesys Backend Genesys Backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Genesys PGR
  • Genesys BackendGenesys Backend
  • Issues
  • #262

Closed
Open
Created Jun 13, 2018 by Matija Obreza@mobrezaOwner

Hazelcast misbehaving with Docker

https://github.com/bitsofinfo/hazelcast-docker-swarm-discovery-spi

Genesys (production) is now configured as two separate services (server and standby) that try to expose the correct names using service names. While this works most of the time, we have a cluster brain-split every few weeks, causing 403 HTTP errors as _crsf tokens are out of sync.

Maybe the best approach would be to add another Hazelcast instance (to 3 in total) as a docker service. This may prevent issues with merging after a brain split.

Edited Jun 18, 2018 by Matija Obreza
Assignee
Assign to
Time tracking