Unblock a locked key after rate limiting

Imported Google Group message. Original thread at: Redirecting to Google Groups Import Date: 2016-01-19 21:35:46 +0000.
Sender:Senthil Muniswamy.
Date:Monday, 14 December 2015 22:10:13 UTC.

Hi Martin,

A key was blocked due to exceeded rate limit threshold. I have updated the key with a different policy from tyk dashboard. Key still results in “Rate limit exceeded” error. I have to manually delete the rate-limit-keyid.BLOCKED key from Redis to make it work.

Is it a bug or am I supposed to configure/reset any other setting?


Imported Google Group message.
Sender:Martin Buhr.
Date:Monday, 14 December 2015 22:23:40 UTC.

Hi Senthil,

The block will expire automatically after the rate limit period (so if it’s 1000 per minute, the block will go after 60 seconds), what kind of rate limit period were you running?

If it’s an instant fix needed, then removing the block manually is the only thing you can do for now.

This is a new rate limiter, it handles rate limits off-thread to reduce latency and uses a block sentinel with an EXP to enforce the limit. The assumption of course is that rate limits are over short periods, so it doesn’t affect usability.

We might want to change the key update function so that the reset quota which happens when a key is updated also removes any outstanding block. Will put it on the roadmap.


From: Senthil Muniswamy [email protected]
Sent: Monday, December 14, 2015 22:10
Subject: Unblock a locked key after rate limiting
To: Tyk Community Support [email protected]

  • show quoted text -

You received this message because you are subscribed to the Google Groups “Tyk Community Support” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web, visit https://groups.google.com/d/msgid/tyk-community-support/2b317bf7-202a-4c2d-8fd9-c382ae38d47a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.