Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

files not loaded occasionally due "another thread has locked it for loading"

Open
#233 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source file or test is named. Start by tracing the batch-loading path that emits “another thread has locked it for loading” and handles ConditionalCheckFailedException, using the reported timeout, batch size, and batchSizeBytes settings. Done means the intermittent skipped-file cause is identified and a verified mitigation or fix is documented.

Written by the indexing model from the issue text.

Description

A small number of my files (around 10 out of 20k) is not loaded each day, with such error being returned after it hits the timeout:

error: The conditional request failed 
{
    "code": "ConditionalCheckFailedException",
    "time": "2021-08-23T21:16:14.506Z",
    "requestId": "5UCMPG1CQ6QRQAATPJPH8V536VVV4KQNSO5AEMVJF66Q9ASUAAJG",
    "statusCode": 400,
    "retryable": false,
    "retryDelay": 25.6182288251398
}

and logging this:

debug: Batch is ready to be processed, but another thread has locked it for loading

Despite the debug log above, I wasn't able to find any other batches with these files. My configuration is:

  • batchTimeoutSecs: 240
  • batchSize: 100
  • batchSizeBytes: ""

I wonder if anyone else experienced similar issue and whether there's a simple config tweak that could be applied to mitigate this? Thanks.

Dominant language
JavaScript
Stars
595
Forks
161
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-lambda-redshift-loader

All issues in awslabs/aws-lambda-redshift-loader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.