eventsourcing/es4j

Problem: PostgreSQL database provisioning contention

Open

#208 opened on Jan 27, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (27 forks)batch import
bughelp wanted

Repository metrics

Stars
 (406 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

PostgreSQL-backed journal & indices will create necessary tables and types without consideration for others — meaning there might be a conflict and two nodes might attempt to do the same thing at the same time.

Proposed solution: ensure these storages are locking these initialization routines. PostgreSQL advisory locks can be used to easily accomplish this.

Contributor guide

Research direction
Implement PostgreSQL advisory locks in the database initialization code to prevent concurrent table creation conflicts.
Tech stack
javapostgresql
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.
Clear
Prerequisites
JavaPostgreSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70