RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[OpenSearch Anomaly Detection] Implement adaptive scaling for AD indices

The system needs adaptive scaling for Anomaly Detection (AD) indices to handle horizontal scalability issues. When scaling clusters (e.g., from 10 to 100 data nodes), the current AD result index shard settings remain static, leading to potential concurrency problems with bulk write requests.

Original Source

@@kaituo | 0 pts | 7/8/2021

**Is your feature request related to a problem? Please describe.** From Yaliang's comment: https://github.com/opensearch-project/anomaly-detection/pull/121#issuecomment-876741491 Have some concern about the horizontal scalability. For example, if user scale cluster from 10 data nodes to 100 data nodes, then will have 100 worker nodes running entities, that means we may send out 100 bulk write AD result requests concurrently. But the AD result index shard setting is still the same, that may bring higher write load and user's general bulk write request may impacted. Confirm with PM/SDM if the concern of horizontal scalable issue is reasonable. **Describe the solution you'd like** We will need adaptive scaling of AD indices to scale index shards when needed. **Describe alternatives you've considered** Throttling index usage at the cost of AD usability.

Discussion

Loading comments...