hcengineering / hcengineering/platform
very high CPU usage if elastic went down and transactor indexer have some work
Open
- Dominant language
- TypeScript
- Stars
- 27.7k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the high CPU condition with Elasticsearch unavailable while the transactor indexer has pending work. Trace the TypeScript transactor/indexer and Elasticsearch failure-handling paths, then verify that the workload no longer causes excessive CPU and that indexing recovers when Elasticsearch returns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, typescript
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100