Redis Enterprise high Connection issue

Open
#15 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
redis
Domain
cloud, databases

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the Redis Enterprise E100 connection and monitoring documentation, focusing on how the 30-day connected-client metric is counted. Done would be a documented explanation of the metric and clear guidance on connection optimization and plan downgrading.

Written by the indexing model from the issue text.

Description

I am looking to optimize the cost for Redis enterprise. Right now i am using an E100 plan When i look at the monitoring metrics i see a low utilization of CPU, low server load and low % memory usage but i see the connected client parameter the sum for last 30days to be very high approx. 2.13M. as per E100 plan 100K connection are allowed but in my case the sum of connections are way too high. What happens in this scenario?

Is there a way to optimize the connections and downgrade to a lower plan to save cost?

Dominant language
PowerShell
Stars
12
Forks
17
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 Azure/AzureCacheForRedis

All issues in Azure/AzureCacheForRedis

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.