|Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||10/10/12 9:08 PM|
The DefaultStoreClient currently in use in production at LinkedIn is a source of a lot of issues. I'm enumerating them below:
* The cluster topology and store metadata has to be synchronized on the client side. This makes bootstrapping (a process by which the client obtains this metadata from a random server node) an expensive operation. In addition, it introduces the additional burden of fetching the latest changes or bouncing the client when such an event occurs.
* Complicated connection management which seems to have operational and performance implications.
* Existing client handles all the replication (including cross zone) which is inefficient.
* The client design is pretty complicated, with multiple levels of nesting.
* Client side config parameters are far too many (sometimes confusing) which causes an operational overhead.
Although some of these issues can be fixed, it requires an iterative release to all the clients. For instance, we have recently implemented an auto-bootstrapper mechanism which tracks changes in cluster.xml happening on the cluster and automatically re-bootstraps the client which helps in doing cluster maintenance. However, in order to reap the benefits, it is essential that all the clients using the cluster pick up this new release. This is a very costly operation when a large number of clients are involved.
Refactor most of the Voldemort logic out of the client and create a new entity called the 'Coordinator'. Essentially we're trying to make the client more lightweight to address most of the issues discussed above.
A high level description of how it will work is as follows:
- We can deploy a set of N coordinators in front of M server nodes (the ration of N:M needs to be worked out).
- The coordinator deployment is symmetric in the sense: each coordinator can satisfy any Voldemort request (get/put/getall/...).
- The coordinator is stateless (across requests) and supports a REST interface.
- When it receives a Voldemort request (get/put/...), it takes care of routing the request to the required server nodes as specified by the store properties, aggregate the result and return an HTTP response.
The coordinator still needs to obtain the cluster.xml and stores.xml, but the point is that its within the control of the administrator (thus, fetching/bouncing is really easy). In addition, all the bug fixes can be quickly deployed due to this property. In summary, this is a huge operational benefit. Please note that the subsequent bug fixes would also be made available as part of the existing thick client (same code path).
The main issue now is how to route a request from the thin client to the coordinator. The ideal solution should take care of the following:
- Fair load balance of the incoming REST requests amongst the N coordinators
- Have the ability to dynamically add / remove / change the coordinator nodes (with minimal impact to the clients)
- Should not have any extra overhead (since every request will route through this piece)
- Should be highly available
At LinkedIn, there is a proprietary solution that resolves the above Open Issue. Unfortunately, the proprietary solution is not open sourced (yet). So we're opening this question to the community: What open source options may resolve our Open Issue?
We will document the detailed design for the coordinator and thin client in a separate wiki. This is just to get some initial feedback from the community regarding the routing logic between the thin client and the coordinator in the long term. If you have any ideas please share with us!
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Sunny Gleason||10/11/12 4:41 AM|
On 10/11/12, Chinmay Soman <chinmay...@gmail.com> wrote:
> At LinkedIn, there is a *proprietary solution* that resolves the above Open
> Issue. Unfortunately, the proprietary solution is not open sourced (yet).> may resolve our *Open Issue*?
You should check out Riak.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||maarten||10/15/12 2:51 AM|
Sounds nice, I have been toying with the idea of putting a REST proxy
for a Voldemort cluster. The elephant in the room is of course how to
shield the resources - i.e. add session management/authN or not.
Using Lift/Scala it should be a few days of work. What is your planning?
> You received this message because you are subscribed to the Google Groups "project-voldemort" group.
> To unsubscribe from this group, send email to project-voldem...@googlegroups.com.
> Visit this group at http://groups.google.com/group/project-voldemort?hl=en.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||10/16/12 2:43 PM|
Currently, we're thinking of using Netty for implementing the REST enabled coordinator and make that part open source. The other component is essentially a software load balancer with a persistent HTTP connection pool which is the core of the thin client. This thin client will be released internal to LinkedIn at first.
But yes, any good load balancing solution (along with a HTTP connection pool) will work in this case. I agree that wont be a lot of work: anyone willing to take this up ?
I'm currently designing the REST API for the coordinator. Since we dont want to do any extra work, the de-compression, de-serialization and inconsistency resolver modules should still be located in the thin client. This means we can only transfer raw bytes between the thin client and the coordinator. In my prototype I'm going to use base64 encoding to send the data to and fro. But are there any specific suggestions with respect to the REST API ?
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||maarten||10/16/12 10:37 PM|
Sounds like were thinking along the same lines. I'm on it, I'll update with a status within a week.
Contact me if you want to discuss this.
To unsubscribe from this group, send email to email@example.com.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||10/18/12 2:46 PM|
Sounds good. I'll have a base prototype coordinator working soon (roughly next week) which speaks a binary protocol on top of HTTP chunked transfer encoding.
We can take it from there. There are a couple of issues with respect to what protocol / schema to use for this communication though. For instance if the messaging layer uses Avro and the keys and values use JSON, then we'll end up doing expensive translations.
We need to standardize this.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||maarten||10/26/12 6:15 AM|
The question is whether speed is an issue on the container level. I am
short on time, but will try to pick things up sooner rather than
Probably profitable to have the two approaches, I guess.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||1/24/13 5:41 PM|
Apologies for the radio silence guys. We've just published the REST API to be used with the coordinator and thin client.
Any comments, concerns are welcome !
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||2/5/13 1:52 PM|
I've updated the design doc here:
The link to the REST API is also at the end of this document. Anybody who wants to implement the REST'ful client in a non Java language should probably go through that PDF and point out mistakes if any.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Alex Feinberg||2/8/13 7:06 PM|
Looks great, I really like this. I like how multi-gets are handled!
> To unsubscribe from this group and stop receiving emails from it, send an email to project-voldem...@googlegroups.com (mailto:firstname.lastname@example.org).
> Visit this group at http://groups.google.com/group/project-voldemort?hl=en.> For more options, visit https://groups.google.com/groups/opt_out.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Tsume||2/18/13 8:36 AM|
Is there a REST'ful client available for use yet? I went through the github code but I didn't see it, except a python implementation (which I'm unsure if it still works properly as I received 404 errors). I've tried creating my own Http client in Jetty but I receive 404 errors as well. A working example would be great to help me figure out what I'm missing
Also, might be a slight oversight, in the API pdf the port number was not indicated for the URI
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Chinmay Soman||2/18/13 11:25 PM|
We're still working on the implementation. There are two key pieces as part of this:
1) Coordinator with the embedded fat client layer
2) Java Rest client
I'll send out a note when the coordinator is ready. At this moment we do not have a plan for a Python client, but once the coordinator is in place, it should be trivial to write one.
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||Vinoth C||2/22/13 9:13 AM|
The biggest advantage of the coordinator is that now the community can chip with clients in different languages... :)
Fun times ahead
|Re: [project-voldemort] Proposal: RESTful coordinator service for the Voldemort cluster||maarten||3/7/13 8:57 AM|
Just saw this, pretty nice. Keep up the good work!