Production deployment

[brk0v (Viacheslav Biriukov)]

@ThomasJ

What I’m struggling to understand is how to distribute the communication and how to properly setup different classes of servers.

As each FDB instance is tied up to a CPU, it also has a different port. So to expose all of them to each other, do you put a proxy in front of it? So lets say I have 8 FDBs per server starting at the port 4500, then do I put a proxy on lets say 3333 in front of them and round-robin distribute the load on the server? Or is this somehow done on the client like it’s with aerospike and couple of others. Additionally, as I have 5 servers, do I again load balance the traffic evenly between all the servers through a proxy or is this done again on a client?

I suspect that both are done one the client through the cluster file, but I’m just guessing here.

Client library of fdb is in charge of all this magic. You just need to provide a proper start point file fdb.cluster with coordinators.

@ThomasJ

What are the best practices when deploying and managing this kind of cluster? I haven’t found any extensive provision scripts (ansible or others), so trying to figure out what’s the best way to do so, especially as the cluster is populated through the cluster file. Do you produce it manually before the deployment and then just distribute it everywhere, or?

I did it manually.

@ThomasJ

And finally, what’s the best structure of the process class in this kind of cluster? I read the guide but still not sure what’s the best, at least initial, structure. Does it depend on the purpose of the cluster?

Look at my topic, there is some info about process classes Segmentation fault error and broken cluster - #17 by brk0v