Comments (5)
@xcl3721 Here are the answers.
- A token along with DC and Rack is like an identifier for a node. Based on this, nodes can know what subset of data they can own. Of course, nodes in different rack/dc can own the same subset of data.
- Look at this script and it gives you an idea how you should generate tokens:
https://github.com/Netflix/dynomite/blob/master/scripts/generate_yamls.py - Answer is similar to #2. Take a look at the output files from that script to understand the topology
- I don't see this is the case. Please explain in more details. Probably you had a wrong configuration somewhere.
- You can read this issue here as it relates to your question:
#51
Furthermore, we are currently working on data repair as additional process to fix bad data.
from dynomite.
thank u sir
can we support php extension like dyo?
my config is here
dyn_o_mite:
datacenter: dc
rack: rack1
dyn_listen: 172.1.1.61:8101
dyn_seed_provider: simple_provider
dyn_seeds:
- 172.1.1.62:8101:rack1:dc:1721162
- 172.1.1.63:8101:rack2:dc:1721161
- 172.1.1.64:8101:rack2:dc:1721162
listen: 0.0.0.0:6399
timeout: 3000
server_retry_timeout: 3000
servers: - 127.0.0.1:6379:1
tokens: '1721161'
secure_server_option: datacenter
server_connections: 4
auto_eject_hosts: true
server_failure_limit: 3
pem_key_file: /etc/dynomite/dynomite.pem
redis: true
dyn_o_mite:
datacenter: dc
rack: rack1
dyn_listen: 172.1.1.62:8101
dyn_seed_provider: simple_provider
dyn_seeds:
- 172.1.1.61:8101:rack1:dc:1721161
- 172.1.1.63:8101:rack1:dc:1721161
- 172.1.1.64:8101:rack1:dc:1721162
listen: 0.0.0.0:6399
timeout: 3000
server_retry_timeout: 3000
servers: - 127.0.0.1:6379:1
tokens: '1721162'
secure_server_option: datacenter
server_connections: 4
auto_eject_hosts: true
server_failure_limit: 3
pem_key_file: /etc/dynomite/dynomite.pem
redis: true
dyn_o_mite:
datacenter: dc
rack: rack2
dyn_listen: 172.1.1.63:8101
dyn_seed_provider: simple_provider
dyn_seeds:
- 172.1.1.61:8101:rack1:dc:1721161
- 172.1.1.62:8101:rack1:dc:1721162
- 172.1.1.64:8101:rack2:dc:1721162
listen: 0.0.0.0:6399
timeout: 3000
server_retry_timeout: 3000
servers: - 127.0.0.1:6379:1
tokens: '1721161'
secure_server_option: datacenter
server_connections: 4
auto_eject_hosts: true
server_failure_limit: 3
pem_key_file: /etc/dynomite/dynomite.pem
redis: true
dyn_o_mite:
datacenter: dc
rack: rack2
dyn_listen: 172.1.1.64:8101
dyn_seed_provider: simple_provider
dyn_seeds:
- 172.1.1.61:8101:rack1:dc:1721161
- 172.1.1.62:8101:rack1:dc:1721162
- 172.1.1.63:8101:rack2:dc:1721161
listen: 0.0.0.0:6399
timeout: 3000
server_retry_timeout: 3000
servers: - 127.0.0.1:6379:1
tokens: '1721162'
secure_server_option: datacenter
server_connections: 4
auto_eject_hosts: true
server_failure_limit: 3
pem_key_file: /etc/dynomite/dynomite.pem
redis: true
and then add new one config--------------
dyn_o_mite:
datacenter: dc
rack: rack
dyn_listen: 172.1.1.66:8101
dyn_seed_provider: simple_provider
dyn_seeds:
- 172.1.1.61:8101:rack1:dc:1721161
- 172.1.1.62:8101:rack1:dc:1721162
- 172.1.1.64:8101:rack2:dc:1721162
- 172.1.1.63:8101:rack2:dc:1721161
listen: 0.0.0.0:6399
timeout: 3000
server_retry_timeout: 3000
servers: - 127.0.0.1:6379:1
tokens: '3333333'
secure_server_option: datacenter
server_connections: 1
auto_eject_hosts: true
server_failure_limit: 3
pem_key_file: /etc/dynomite/dynomite.pem
redis: true
from dynomite.
Sorry but we don't have the resource for PHP client like Dyno at this time.
However, you can just use any Redis PHP client and take care of the failover in your application layer yourself?
from dynomite.
ok
:) ~ thank u~
from dynomite.
How can we achieve failover in application layer using PHP redis client ?
Any hints.. !!
Thanks
Mahesh
from dynomite.
Related Issues (20)
- proxy_accept:173 accept on PROXY 8 failed: Too many open file
- TEST: Redis Commands Supported HOT 1
- Dynomite logs missing HOT 2
- Make error in Debian 11: multiple definition of C2G_OutQ HOT 1
- unsupported command 'SELECT' HOT 3
- Incorrect Privilege Assignment
- brew install dynomite
- Replication is not working from appication/client side HOT 1
- Build breaks on armv6, armv7
- Warning messages when building from source
- AUTH command not supported HOT 1
- Dynomite POC question
- ERR Storage: Datastore refused connection HOT 1
- DEL/HDEL commands return (nil).
- error: incompatible pointer to integer conversion initializing 'int' with an expression of type 'void *'
- question about config dynomite described in wiki HOT 1
- Har du opp
- dynomite tokens
- SADD inconsistency HOT 1
- Dynomite / Redis Metrics
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dynomite.