[global-rate-limit] [memcached] cant put more then 1 host

[kfirfer]

Hello,

When I try to put more than 1 memcached host, the global rate limit isn't working and doesn't communicate with memcached instance(s)

Configmap:

    global-rate-limit-memcached-host: "memcached-stack-0.memcached-stack.ingress-nginx.svc.cluster.local,memcached-stack-1.memcached-stack.ingress-nginx.svc.cluster.local"
    global-rate-limit-memcached-port: "11211"

App version: 0.44.0
Helm chart version: 3.23.0

[aledbf]

/assign @ElvinEfendi

[ElvinEfendi]

Hey @kfirfer, we rely on https://github.com/openresty/lua-resty-memcached which does not support clustering and also it seems like it will never does given author's this thought: openresty/lua-resty-memcached#18 (comment)

The underlying library ingress-nginx uses for global throttle is https://github.com/ElvinEfendi/lua-resty-global-throttle. I'll create an issue there to implement clustering using https://github.com/openresty/lua-resty-balancer/blob/master/lib/resty/chash.lua. Feel free to send a patch.

EDIT: I created the issue in the upstream library: ElvinEfendi/lua-resty-global-throttle#27

[kfirfer]

@ElvinEfendi
Thanks for clarification !

[ElvinEfendi]

np @kfirfer !

This should not be labelled as a bug though. The feature never advertised that it supports clustered memcached.

[kfirfer]

@ElvinEfendi
You right, I don't know how to change labels =X

[ElvinEfendi]

/remove-kind bug

[iamNoah1]

/kind design

[iamNoah1]

/remove-kind design
/kind feature

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[iamNoah1]

@kfirfer is this still relevant for you?

[iamNoah1]

/close

Closing due to inactivity. Feel free to open a new issue.

[k8s-ci-robot]

@iamNoah1: Closing this issue.

In response to this:

/close

Closing due to inactivity. Feel free to open a new issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.