Just came across corvus and was wondering if you could clarify how to use it ? <p

There're some modified and unsupported commands, see <a href="https://github.com/eleme

thanks <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-u

thanks so i only need <div class="snippet-clipboard-content notranslate position-r

how to use corvus ? about corvus HOT 6 CLOSED

eleme commented on July 19, 2024

how to use corvus ?

from corvus.

Comments (6)

doyoubi commented on July 19, 2024 1

Corvus is just a redis protocol proxy and can't build a cluster itself. It serve between the clients and redis cluster so that clients don't need to support redis cluster protocol.
You have already successfully runned it. slot map updated: corverd 16384 slots means corvus is ready to serve. Now you can use any redis client to connect to corvus (0.0.0.0:12345 in your case) and just treat it like a redis 2.x .

$ redis-cli -p 12345 GET key

from corvus.

doyoubi commented on July 19, 2024 1

There're some modified and unsupported commands, see readme for details. As multi-key commands are splitted into sub commands for performance, they don't satisfy atomicity and isolation any more.
Corvus will find all the masters itself by sending CLUSTER NODES to redis cluster, so you don't need to fill all the nodes in the node field of config file. But when you remove some nodes from the cluster, make sure that there's at least one existing node in the config file.

from corvus.

centminmod commented on July 19, 2024

ah so i must make the cluster first and node array is for each cluster's master ?

i setup 9 redis server 3x sets of 1x master + 2x slaves

./redis-generator.sh 9 cluster

join them to a redis cluser


redis-cluster-tool -C "cluster_create 127.0.0.1:6479[127.0.0.1:6480|127.0.0.1:6481] 127.0.0.1:6482[127.0.0.1:6483|127.0.0.1:6484] 127.0.0.1:6485[127.0.0.1:6486|127.0.0.1:6487]"
Waiting for the nodes to join...
All nodes joined!
Cluster created success!

change corvus.conf

node 127.0.0.1:6479,127.0.0.1:6482,127.0.0.1:6485

start corvus

src/corvus /etc/corvus/corvus.conf 
2017-03-15 04:21:49,561 DEBUG [default 12345 31183 31183]: Registering signal[Interrupt] (corvus.c:62)
2017-03-15 04:21:49,562 DEBUG [default 12345 31183 31183]: Registering signal[Terminated] (corvus.c:62)
2017-03-15 04:21:49,562 DEBUG [default 12345 31183 31183]: Registering signal[Segmentation fault] (corvus.c:62)
2017-03-15 04:21:49,562 INFO [default 12345 31183 31183]: starting slot manager thread (slot.c:533)
2017-03-15 04:21:49,562 DEBUG [default 12345 31183 31185]: slowlog enabled (corvus.c:256)
2017-03-15 04:21:49,562 DEBUG [default 12345 31183 31186]: slowlog enabled (corvus.c:256)
2017-03-15 04:21:49,564 INFO [default 12345 31183 31183]: serve at 0.0.0.0:12345 (corvus.c:481)
2017-03-15 04:21:49,563 DEBUG [default 12345 31183 31187]: slowlog enabled (corvus.c:256)
2017-03-15 04:21:49,565 INFO [default 12345 31183 31184]: updating slot map using 127.0.0.1:6479 (slot.c:290)
2017-03-15 04:21:49,564 DEBUG [default 12345 31183 31188]: slowlog enabled (corvus.c:256)
2017-03-15 04:21:49,567 INFO [default 12345 31183 31184]: slot map updated: corverd 16384 slots (slot.c:353)

???

from corvus.

centminmod commented on July 19, 2024

thanks @doyoubi for the clarification. When you mean treat it like redis 2.x, are there some limitations if using redis 3.x servers ?

also is it correct to use

node 127.0.0.1:6479,127.0.0.1:6482,127.0.0.1:6485

where redis cluster is 3x masters on 6479, 6482, 6485 ?

from corvus.

centminmod commented on July 19, 2024

thanks so i only need

node 127.0.0.1:6479

from my redis cluster ?

from corvus.

doyoubi commented on July 19, 2024

Yes, but I recommand adding all the nodes on it.

from corvus.

how to use corvus ? about corvus HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent