apache / apache/couchdb

Ensure full commit timing out on replication of large database

Open
#4,639 13 comments 0 reactions 0 assignees View on GitHub
bug needs-triage
Dominant language
Erlang
Stars
7k
Forks
1.1k
Avg merge
1d 16h
Merged PRs (30d)
9

Description

[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )

## Description
I am trying to replicate the npm registry through couchdb. However, I keep getting the following errors:

{"error":"checkpoint_commit_failure","reason":"Failure on source commit: {'EXIT',{http_request_failed,\"POST\",\n \"https://skimdb.npmjs.com/registry/_ensure_full_commit\",\n {error,{error,req_timedout}}}}"}

[NOTE]: # ( Describe the problem you're encountering. )
[TIP]: # ( Do NOT give us access or passwords to your actual CouchDB! )

## Steps to Reproduce

I am using version 3.3.2. When post a request to the _ensure_full_commit endpoint, it returns something that looks like this:

{"ok":true,"instance_start_time":"1686442464"}

However, based on the documentation, it should be returning an instance start time of 0.

[NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )

## Expected Behaviour

[NOTE]: # ( Tell us what you expected to happen. )

## Your Environment

[TIP]: # ( Include as many relevant details about your environment as possible. )
[TIP]: # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. )

{"couchdb":"Welcome","version":"3.3.2","git_sha":"11a234070","uuid":"358bddb8b0671d6dc8774db0a626edef","features":["access-ready","partitioned","pluggable-storage-engines","reshard","scheduler"],"vendor":{"name":"The Apache Software Foundation"}}

* CouchDB version used:
* Browser name and version:
* Operating system and version:

## Additional Context

[TIP]: # ( Add any other context about the problem here. )

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the replication failure against the _ensure_full_commit endpoint on CouchDB 3.3.2 and compare its response with the documented instance start time. Trace the checkpoint commit timeout and determine what behavior should be considered correct; done means large-database replication no longer times out and the endpoint response matches the documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.