questdb / questdb/nodejs-questdb-client

Inserting data from more than one script/pm2 process causes Web console to refuse connection

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
48
Forks
12
Avg merge
17d 10h
Merged PRs (30d)
1

Description

Hi,

I have just managed to code a script that pulls data from an API and inserts into my questdb. I am using PM2 to manage the processes where each process runs at every second.

I have setup 4 processes to pull data from 4 different markets and the moment I have all 4 running, when I try to visit web console it gives me a refused connection. Dialling back PM2 to 1 process only and I can login just fine.

Is there a limitation on clients connected somewhere that I can change?

It seems everything grinds to a halt the moment I have all 4 script inserting data

Here is a gist:

https://gist.github.com/hmpmarketing/b18ba2b6db4fb0af370fbfea1f49c366

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no repository files or tests; start by reviewing the linked gist and reproducing the refused Web console connection with one versus four PM2 processes. Trace the client requests and QuestDB interaction to identify the limiting or failure condition, then verify that concurrent inserts no longer make the console unreachable.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, typescript
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.