Reverbrain wiki

Site Tools


backrunner:uri

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
backrunner:uri [2017/02/09 16:42]
zbr [/upload/]
backrunner:uri [2017/02/11 09:25] (current)
zbr [/upload/]
Line 104: Line 104:
 This handler will write data into particular bucket (if it exists), and no automatic bucket selection will be performed. It is possible that elliptics nodes in given bucket are already fully filled and this write may fail. This handler will write data into particular bucket (if it exists), and no automatic bucket selection will be performed. It is possible that elliptics nodes in given bucket are already fully filled and this write may fail.
  
 +If you want to overwrite data, and some groups which belong to specified bucket are not accessible, upload still returns success, and when later missing servers come online, replicas will not be consistent. Elliptics does not automatically runs recovery when node goes online, since it usually adds more load to the system which was likely the reason nodes went offline at the first place. This will only be fixed after elliptics recovery.
  
 +It is generally a very bad idea to update data in eventually consistent systems, consider switching to the case when you only upload new keys and never overwrite existing, in this case missing data will be automatically recovered on the first read.
 +
 +You still can use so called //​read-latest//​ feature to read the latest data among all potentially inconsistent replicas, which adds noticeable overhead, basically it reads metadata from all the replicas, selects the most recently updated data and reads it.
 ==== /get/ ==== ==== /get/ ====
  
backrunner/uri.txt ยท Last modified: 2017/02/11 09:25 by zbr