phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Batyrshin <0x62...@gmail.com>
Subject Re: java.io.IOException: Added a key not lexically larger than previous
Date Thu, 15 Aug 2019 20:31:11 GMT
> Since you're using a global index, which stores the index data in a separate table (and
hence different regions, each of which has a different MemStore / set of HFiles), and the
error's happening to the base table, I'd be surprised if Phoenix indexing is related. 

AFAIK Phoenix handle mutable secondary global index server side via coprocessor on HBase put.
So maybe this coprocessor some how brake MemStore consistency for example by releasing locks/etc.


> What coprocessors (Phoenix and otherwise) are loaded on the table?


TABLE_ATTRIBUTES => {
    MAX_FILESIZE => '32212254720',
    coprocessor$1 => '|org.apache.phoenix.coprocessor.ScanRegionObserver|805306366|',
    coprocessor$2 => '|org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver|805306366|',
    coprocessor$3 => '|org.apache.phoenix.coprocessor.GroupedAggregateRegionObserver|805306366|',
    coprocessor$4 => '|org.apache.phoenix.coprocessor.ServerCachingEndpointImpl|805306366|',
    coprocessor$5 => '|org.apache.phoenix.hbase.index.Indexer|805306366|org.apache.hadoop.hbase.index.codec.class=org.apache.phoenix.index.PhoenixIndexCodec,index.builder=org.apache.phoenix.index.PhoenixIndexBuilder'
}


Mime
View raw message