scan ‘tsdb’ failed from on hbase shell

I’m using  opentsdb for my real time and little data.  I created 4 table for tsdb . I used  create-table sh  from in opentsdb directory for can create this tables. I want to scan on ‘tsdb’ table  but  hbase  give me  this error;

 


=> ["edr", "flowstat", "log", "ozge_log", "ozge_log2", "ozge_switch", "testtable", "tsdb", "tsdb-meta", "tsdb-tree", "tsdb-uid"]

hbase(main):002:0> scan 'tsdb'

ROW COLUMN+CELL
ERROR: No server address listed in hbase:meta for region tsdb,,1500907631012.82b3e5b7a9076f98c84b5bd1dff9d510. containing row
Here is some help for this command:

Scan a table; pass table name and optionally a dictionary of scanner

specifications. Scanner specifications may include one or more of:

TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, ROWPREFIXFILTER, TIMESTAMP,

MAXLENGTH or COLUMNS, CACHE or RAW, VERSIONS, ALL_METRICS or METRICS
If no columns are specified, all columns will be scanned.

To scan all members of a column family, leave the qualifier empty as in

'col_family'.
The filter can be specified in two ways:

1. Using a filterString - more information on this is available in the

Filter Language document attached to the HBASE-4176 JIRA

2. Using the entire package name of the filter.
If you wish to see metrics regarding the execution of the scan, the

ALL_METRICS boolean should be set to true. Alternatively, if you would

prefer to see only a subset of the metrics, the METRICS array can be

defined to include the names of only the metrics you care about.
Some examples:
hbase> scan 'hbase:meta'

hbase> scan 'hbase:meta', {COLUMNS => 'info:regioninfo'}

hbase> scan 'ns1:t1', {COLUMNS => ['c1', 'c2'], LIMIT => 10, STARTROW => 'xyz'}

hbase> scan 't1', {COLUMNS => ['c1', 'c2'], LIMIT => 10, STARTROW => 'xyz'}

hbase> scan 't1', {COLUMNS => 'c1', TIMERANGE => [1303668804, 1303668904]}

hbase> scan 't1', {REVERSED => true}

hbase> scan 't1', {ALL_METRICS => true}

hbase> scan 't1', {METRICS => ['RPC_RETRIES', 'ROWS_FILTERED']}

hbase> scan 't1', {ROWPREFIXFILTER => 'row2', FILTER => "

(QualifierFilter (>=, 'binary:xyz')) AND (TimestampsFilter ( 123, 456))"}

hbase> scan 't1', {FILTER =>

org.apache.hadoop.hbase.filter.ColumnPaginationFilter.new(1, 0)}

hbase> scan 't1', {CONSISTENCY => 'TIMELINE'}

For setting the Operation Attributes

hbase> scan 't1', { COLUMNS => ['c1', 'c2'], ATTRIBUTES => {'mykey' => 'myvalue'}}

hbase> scan 't1', { COLUMNS => ['c1', 'c2'], AUTHORIZATIONS => ['PRIVATE','SECRET']}

For experts, there is an additional option -- CACHE_BLOCKS -- which

switches block caching for the scanner on (true) or off (false). By

default it is enabled. Examples:
hbase> scan 't1', {COLUMNS => ['c1', 'c2'], CACHE_BLOCKS => false}
Also for experts, there is an advanced option -- RAW -- which instructs the

scanner to return all cells (including delete markers and uncollected deleted

cells). This option cannot be combined with requesting specific COLUMNS.

Disabled by default. Example:
hbase> scan 't1', {RAW => true, VERSIONS => 10}
Besides the default 'toStringBinary' format, 'scan' supports custom formatting

by column. A user can define a FORMATTER by adding it to the column name in

the scan specification. The FORMATTER can be stipulated:
1. either as a org.apache.hadoop.hbase.util.Bytes method name (e.g, toInt, toString)

2. or as a custom class followed by method name: e.g. 'c(MyFormatterClass).format'.
Example formatting cf:qualifier1 and cf:qualifier2 both as Integers:

hbase> scan 't1', {COLUMNS => ['cf:qualifier1:toInt',

'cf:qualifier2:c(org.apache.hadoop.hbase.util.Bytes).toInt'] }
Note that you can specify a FORMATTER by column only (cf:qualifier). You cannot

specify a FORMATTER for all columns of a column family.
Scan can also be used directly from a table, by first getting a reference to a

table, like such:
hbase> t = get_table 't'

hbase> t.scan
Note in the above situation, you can still provide all the filtering, columns,

options, etc as described above.

How  can I resolve this problem?

Özge Ayaz Şef on 24 Temmuz 2017 yazdı
Yorum Ekle
  • 1 Yanıt(lar)

    http://portal.venidera.com/kb/2016/11/25/english-cleaning-opentsdb-schema-on-hbase-normal-and-crash-situations/?lang=en

    Özge Ayaz Şef on 24 Temmuz 2017 yanıtladı
    Yorum Ekle
  • Yanıtınız

    Cevabınızı göndererek Gizlilik Politikası ve Hizmet Şartlarını kabul ediyorsunuz.