Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a optimize for realtime query #924

Open
haike1363 opened this issue Jan 23, 2017 · 2 comments
Open

a optimize for realtime query #924

haike1363 opened this issue Jan 23, 2017 · 2 comments
Labels

Comments

@haike1363
Copy link

hi opentsdb is very good
recently I met a problem:
I want query recently 10 seconds data, example startTime=2017/01/23 19:59:49 endTime=2017/01/23 19:59:59, HBase will return 【 2017/01/23 19:00:00~2017/01/23 19:59:59 】 data, so if more querys the network is full
I slove this problem by set Scanner timeRange
step1:set PutRequest's timestamp
step2:set Scanner timestamp range
if(enable_time_filter_begin) {
scanner.setMinTimestamp(startTime-1);
}
if(enable_time_filter_end) {
scanner.setMaxTimestamp(endTime+1);
}
it make network 100MB/S to little than 10MB/s, it works good

if you add this feature to opentsdb, all the world will be happy!
Looking forward to your reply, best wishes!

@manolama
Copy link
Member

Hi, could you paste the config for your TSDB table in HBase? You can try setting the table config to VERSIONS = 1. The max and min timestamps refer to the column times and should rarely be an issue unless:

a) You have TSD compactions enabled and have multiple TSDs running and re-compacting the same row
b) The same data points (same timestamp) are being written multiple times so that there are multiple versions of the column.

Do either of those situations apply?

@IDerr
Copy link

IDerr commented Sep 21, 2017

Hi, @haike1363
if you question has been answered, could you please close this issue ?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants