Systems and methods for leader node election in cluster server configurations
Disclosed are systems and methods for leader node election, comprising a cluster system including a plurality of nodes, a node registry, wherein nodes are configured to transmit registration requests to the node registry, receive node data is response, and to determine a leader node based on the earliest registered node, and wherein the leader node is configured to dynamically allocate data slots between the plurality of nodes, and each of the nodes are configured to store data associated with allocated data slots in an in-memory least recently used component and data associated with all of the data slots in a persistent storage component.
1. A node management system, comprising:
a first node including a memory and one or more shards, wherein the first node is configured to:
identify one of the one or more shards based on a client request,
retrieve shard rules of the identified shard,
determine an allocation of one or more memory slots of the identified shard based on the client request,
lock the one or more memory slots, and
perform one or more operations on the one or more memory slots associated with the client request based on the allocation.
2. The node management system of claim 1 , wherein the first node is configured to unlock the one or more memory slots.
3. The node management system of claim 1 , wherein the one or more memory slots represent a portion of an in memory least-recently used (LRU) component of the first node.
4. The node management system of claim 1 , further comprising a client device in data communication with the first node, wherein the client request is received from the client device.
5. The node management system of claim 1 , wherein the first node is further configured to:
determine an allocation of one or more database slots of the identified shard;
lock the one or more database slots; and
perform one or more operations on the one or more database slots based on the allocation.
6. The node management system of claim 5 , wherein the one or more database slots represent one or more column families of a persistent storage component of the first node.
7. The node management system of claim 6 , wherein the first node is further configured to back up the persistent storage component of the first node into a backup persistent storage.
8. The node management system of claim 1 , wherein the first node is further configured to update a memory slot associated with the one or more memory slot based on the shard rules.
9. The node management system of claim 1 , wherein the first node is configured to: store an index of one or more keys processed by the first node; and
retrieve a backup of data stored in the shard based on the index.
10. The node management system of claim 1 , further comprising a second node, wherein the first node is further configured to asynchronously update the second node when the second node is an in-region node.
11. A node management method implemented in a node managing system comprising a first node, wherein the first node includes a memory comprising one or more shards, the method comprising:
identifying one of the one or more shard based on a client request;
retrieving shard rules of the identified shard;
determining an allocation of one or more memory slots of the identified shard based on the client request;
locking the one or more memory slots; and
performing one or more operations on the one or more memory slots associated with the client request based on the allocation.
12. The node management method of claim 11 , further comprising:
determining an allocation of one or more database slots of the identified shard,
locking the one or more database slots,
performing one or more operations on the one or more database slots based on the allocation; and
unlocking the one or more database slots.
13. The node management method of claim 11 , further comprising:
performing a hash function on a key in the client request and a modulo operation to determine the allocation of the one or more memory slots.
14. The node management method of claim 13 , wherein the modulo operation is based on an available number of memory slots in the identified shard.
15. The node management method of claim 13 , further comprising identifying the one of the one or more shard based on one of a header or footer of the key in the client request or a container name of a client certificate associated with the client request.
16. A non-transient computer readable medium having instructions stored thereon that, when executed by a node managing system comprising a first node, wherein the first node includes a memory comprising one or more shards, cause the node managing system to perform procedures comprising:
identifying one of the one or more shard based on a client request;
retrieving shard rules of the identified shard;
determining an allocation of one or more memory slots of the identified shard based on the client request;
locking the one or more memory slots; and
performing one or more operations on the one or more memory slots associated with the client request based on the allocation.
17. The non-transient computer readable medium of claim 16 , wherein the shard rules comprise one of a cache capacity and a number of shards.
18. The non-transient computer readable medium of claim 16 , wherein the one or more operations comprise one of a read, write, update, push, or pull request.
19. The non-transient computer readable medium of claim 16 , the procedure further comprises:
encrypting a value associated with the memory slot associated with the client request; and
storing the encrypted value in the memory slot.
20. The non-transient computer readable medium of claim 16 , wherein the node managing system comprises a second node and the procedure further comprises asynchronously updating the second node when the second node is an in-region node on a periodic basis.