All issues

Search results

Should not return "key does not exist" during elasticity action

post-move

Status: Open.

#75 In cw75/tiered-storage;

· cw75 opened on Jul 6, 2018

consider changing request lifecycle

Status: Open.

#68 In cw75/tiered-storage;

· vsreekanti opened on Jul 5, 2018

consider having routing and server in a single process

Status: Open.

#67 In cw75/tiered-storage;

· jhellerstein opened on Jul 5, 2018

Don't track data access for all keys

post-move

Status: Open.

#64 In cw75/tiered-storage;

· cw75 opened on Jul 5, 2018

All parameters should be PUT into kvs when we bootstrap

post-move

Status: Open.

#50 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Parallel hash join

Status: Open.

#45 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Failure handling of function calls

Status: Open.

#44 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Clean Node Shutdown

Status: Open.

#43 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Function Placement & Load Monitoring

Status: Open.

#42 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Hierarchical Namespaces

post-move

Status: Open.

#41 In cw75/tiered-storage;

· cw75 opened on Jul 3, 2018

Node failure and respawn should force re-gossip of data

post-move

Status: Open.

#32 In cw75/tiered-storage;

· cw75 opened on Feb 1, 2018

Store cluster soft state (i.e., tier’s global hash ring) in S3 for availability

post-move

Status: Open.

#30 In cw75/tiered-storage;

· cw75 opened on Feb 1, 2018