Oh boy... a lot of that is beyond me, but I'm glad Redis is introducing clustering 😄

@julian That's the version I have. And it seems to be fixed (maybe a cache issue)

I think Mongo has better failure recovery too, because everything is stored on the disk instead of in RAM.

@julian It seemed pretty straight forward in my mind is the worst part.

Yup, I want this server to be this other server's pathetic little slave and take orders all day...Wha?.....It's rebelling!
It's hard to beat the incorrect logic of something you know absolutely should work as you're telling it to.

Glad I could help 🙂

Considering Redis' clustering is strictly master-slave and doesn't support multi-master, it would be nice to be able to read and write from different Redis instances.

A very basic example: reading from the local Redis slave while writing to an external Redis master. Compared to the current situation (reading from and writing to the same Redis instance, which has to be the master because you can't write to slaves), this would result in data being returned faster from the local slave and the load on the remote master would be lowered.

Some potential failover situations:

Master up, slave(s) down: Read from the Master instead of the slaves Master up, one of many slaves down: Read from the node specified in the config as failover for this one, if not configured read from other slave, if all slaves are down read from master. Master down, slave(s) up: Enter a StackOverflow-esque read-only mode, 503 all requests to the yet-to-be-written Write API.

@baris oh sweet! 🙂

Thanks, @a_5mith that got me running again!

@julian oh tnx

I'm trying to create a user via php to be recognized by nodebb authentication form. I do this via predis, so I can talk to redis via php.
This is the relevant part of the code that creates a user in redisdb for nodebb in php: http://pastebin.com/GZWFvuWc

But sadly, when I tried to login with such created account via php it didn't work and said "User does not exists".
I checked all 'legit' userdata with my userdata created by php and I can't detect any flaws

This is what I told php to create in redis, it's all verified and there:

populate 'user:#' with 22 key's where # is uid populate 'email:uid' with user email and uid populate 'group:registered-users:members' with uid populate 'users:joindate' with 0 and uid populate 'users:joindate' with 0 and uid populate 'users:postcount' with 0 and uid populate 'reputation' with 0 and uid populate 'username:uid' with username and uid populate 'userslug:uid' with userslug and uid

What am I missing :C??? I checked redis and the data is all their, but nodebb says the user does not exists

EDIT: I checked the users tab in admin and saw that the username is there that was created from php. After I press the save button on the profile edit page of that profile, that account can then login! how strange. I'm going to do more digging until someone knows what i'm missing here.

EDIT 2: I forgot slugifying userslug:uid in redis. Finally fix it 🙂

Digital Ocean or vultr 5$ works fine 🙂

Link Preview Image use replicaset if configured by Icehunter · Pull Request #3091 · NodeBB/NodeBB

I use a replicaset. Here's a patch to use as well. config.json: { "url": "http://localhost:4567", "secret": "fae93eb7-f17b-429d-a614-4783d8466517", "database": "mongo", "mongo": { "host": "127.0.0.1,127.0.0.1,127.0.0.1", "port": "27017,27018,27019", "username": "", "password": "", "database": "nodebb" } }

favicon

GitHub (github.com)

Made a pull request for it.

@a_5mith

I chose Digital Ocean server with redis db. There is no problem when 60 users are online.