Issues

On the save action, check if the object is in the local dictionary first, and in case of don't be in the local dict, check if is in another node, or in the permanent storage system before create it

#10

· alonsovidales opened

on Oct 21, 2012

Create an ftp permanent storage access object instead of an S3 based

#9

· alonsovidales opened

on Oct 20, 2012

Create a README file to explain the installation, configuration, and execution, and the allowed messages

#8

· alonsovidales opened

on Oct 13, 2012

A new message like {p, <object_id>} will persist on S3 immediately an object with id object_id

#7

· alonsovidales opened

on Oct 13, 2012

The node asked for an object will load an object from S3 if the object is not found on the ring of nodes

#6

· alonsovidales opened

on Oct 13, 2012

Create a system to dump an object to S3 keeping the consistency

#5

· alonsovidales opened

on Oct 13, 2012

If a node doesn't have connection with the master manager, will try to connect with the slave manager, and in case of can't connect with both, will try to dump all the objects to S3, if the node can't dump the objects after X second, the node will flush t

#4

· alonsovidales opened

on Oct 13, 2012

The slave manager should to check each second if the master node is alive, and incase of a down, it will take the control

#3

· alonsovidales opened

on Oct 13, 2012

The objects will have a flag called dirty in order to specify if the object is modified or not

#2

· alonsovidales opened

on Oct 13, 2012

The system should to automatically dump each object to S3 each X mins if the object was modified, if the object is dirty

#1

· alonsovidales opened

on Oct 13, 2012

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

On the save action, check if the object is in the local dictionary first, and in case of don't be in the local dict, check if is in another node, or in the permanent storage system before create it

Create an ftp permanent storage access object instead of an S3 based

Create a README file to explain the installation, configuration, and execution, and the allowed messages

A new message like {p, <object_id>} will persist on S3 immediately an object with id object_id

The node asked for an object will load an object from S3 if the object is not found on the ring of nodes

Create a system to dump an object to S3 keeping the consistency

If a node doesn't have connection with the master manager, will try to connect with the slave manager, and in case of can't connect with both, will try to dump all the objects to S3, if the node can't dump the objects after X second, the node will flush t

The slave manager should to check each second if the master node is alive, and incase of a down, it will take the control

The objects will have a flag called dirty in order to specify if the object is modified or not

The system should to automatically dump each object to S3 each X mins if the object was modified, if the object is dirty

Search results