Layout Strategy

The layout strategy is responsible for routing and/or broadcasting the appropriate operations to the correct shards in the table to maintain a consistent view of the data in the index.

Hash Strategy

The hash strategy will be configured with a field name that will be required in every document. The field with the hash field name will have it's value hashed and that will determine the shard that the document will be routed for all operations.

Random Strategy

The random strategy will random choose a shard to house the document. However delete, add, and update operations will have to be broadcast to all the shards in the table. So mutate operations may be slower at hit load then the Hash Strategy because more operations have to be sent to the cluster.

Strategy

Number Of Shards

Delete

Update (Delete Phase)

Update (Add Phase)

Add

Search

Hash

Fixed

Single Shard* / Broadcast

Single Shard* / Broadcast

Single Shard*

Single Shard*

Single Shard* / Broadcast

Random

Variable

Broadcast

Broadcast

Broadcast

Broadcast

Broadcast

Single Shard* - Only if the Term or Query contains the defined field that the hash is to operate on.

LayoutStrategy (last edited 2013-01-20 19:41:46 by AaronMcCurry)