-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After the first failure, there will be no further attempts to pursue it. #190
Comments
server:
port: 6380
spring:
application:
name: camellia-redis-proxy-server
camellia-redis-proxy:
console-port: 16379
password: pass123
monitor-enable: false
monitor-interval-seconds: 60
plugins:
- monitorPlugin
- bigKeyPlugin
- hotKeyPlugin
transpond:
type: local
local:
type: simple
resource: redis://@127.0.0.1:6379
redis-conf:
preheat: false you can sett config |
OK! thanks for the reply I will give it a try. |
It seems not working :( cat /opt/redis-proxy/BOOT-INF/classes/application.yml|grep -v ^# server:
port: 6380
spring:
application:
name: camellia-redis-proxy-server
camellia-redis-proxy:
#port: 6380 #priority greater than server.port, if missing, use server.port; if setting -6379, proxy will choose a random port
#application-name: camellia-redis-proxy-server #priority greater than spring.application.name, if missing, use spring.application.name
console-port: 26379 #console port, default 16379, if setting -16379, proxy will choose a random port, if setting 0, will disable console
password: password #password of proxy, priority less than custom client-auth-provider-class-name
monitor-enable: false #monitor enable/disable configure
monitor-interval-seconds: 60 #monitor data refresh interval seconds
plugins: #plugin list
- monitorPlugin
- bigKeyPlugin
- hotKeyPlugin
transpond:
type: local #local、remote、custom
local:
type: simple #simple、complex
resource: redis-cluster://@192.168.5.102:10001,192.168.5.102:10002,192.168.5.102:10003,192.168.5.102:10004,192.168.5.102:10005,192.168.5.102:10006
redis-conf:
preheat: false #preheat upstream redis-connection, default true |
you maybe should use custom transpond.type, see: |
in my test case the redis-cluster where boot up after the redis-proxy.service (systemd unit file) why custom?
is JUST a redis HA ,aka 6 instance (1 replicas) with --cluster create --cluster-replicas 1 is it Is there any difference with 配置application.yml, 如下:
server:
port: 6380
spring:
application:
name: camellia-redis-proxy-server
camellia-redis-proxy:
password: pass123
transpond:
type: local
local:
type: simple
resource: redis-cluster://@127.0.0.1:6379,127.0.0.1:6378,127.0.0.1:6377 |
in custom mode proxy will not to verify availability of upstream redis-cluster |
Module: [e.g. camellia-redis-proxy、camellia-delay-queue]
camellia-redis-proxy
Content: [e.g. need xxxx]
when redis not ok then start camellia-redis-proxy failure, there will be no further attempts to pursue upstream.
Even redis there OK ! camellia-redis-proxy will not brave pursuit!
Log
error.log
The text was updated successfully, but these errors were encountered: