Effects on time ordered SEP events on horizontal scaling

[Pankil]

Hi,

As per my understanding, its very easy to scale hbase-indexer by adding new nodes. I want to know will that affect SEP Event processing on time ordered.

For eg:

T1 -> SEP 1

T2 -> SEP 2

T3 -> SEP 3

T4 -> SEP 4

Consider sep events coming in at T1 to T4 intervals. If they go to 4 different nodes of hbase-indexer process and there can be possibility that they end up in solr in different order. Is that a possibility?

As that will be issue if events are for same rowid and last state of row in hbase would be different than what we have in solr.

Can anyone throw some light in this area?

Pankil

[Gabriel Reid]

Hi Pankil,

A single region server will replicate all data to a single
hbase-indexer node. Within a single hbase-indexer node, processing
order is guaranteed for a single given row. This means that updates
for a single row will be sent to Solr in the same order that they are
written to the WAL in the source HBase region server.

The one exception to this rule is in the case of the redistribution of
regions over the region servers, and/or the addition/removal of
hbase-indexer nodes. When this happens, the pairing of source region
servers to hbase-indexers can change, and during this change if two
updates for a single row are performed, it is possible that they would
be written to Solr out of order.

- Gabriel

> --
> You received this message because you are subscribed to the Google Groups
> "HBase Indexer Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hbase-indexer-u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.