Search Hadoop and all its sub project:

Switch to Threaded View
Subject: Re: HBase timestamp consistency aross multiple region servers?
This is kind of a Y answer to an X-Y question.

I want to use time stamp to order the updates by time. These updates

but I guess that counter table might become a hot spot since

There are two possible answers to this question as posed.

1. You want HBase to order your updates by timestamp. This happens

It is already strongly recommend that you run NTP on all of your HBase
servers as a matter of good distributed system hygiene.  If you don't
specify a specific timestamp in your mutations then HBase will use the
latest server time when persisting your values, and you will have updates
ordered by time.
2. You want to retrieve updates by timestamp. In other words, you don't
merely want HBase to order updates by time you also want to have a time
component as row key or part of a composite row key.

There are several schema design solutions to this. You can use Apache
Phoenix with salted keys. You can use Sematext's HBaseWD library. You can
use a separate distributed process for time ordered keys (strictly
speaking, k-ordered) such as Twitter's Snowflake. Choose one that looks
like it would work best for your use case.

On Fri, Mar 14, 2014 at 2:01 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB