phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao Wang (Jira)" <>
Subject [jira] [Updated] (PHOENIX-5861) Delete index data failed,due to pool closed
Date Tue, 21 Apr 2020 06:50:00 GMT


Chao Wang updated PHOENIX-5861:
    Attachment:     (was: PHOENIX-5861.4.13.x-HBASE.1.3.x.001.patch)

> Delete index data failed,due to pool closed
> -------------------------------------------
>                 Key: PHOENIX-5861
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.13.1
>            Reporter: Chao Wang
>            Priority: Critical
>         Attachments: PHOENIX-5861.4.13.x-HBASE.1.3.x.001.patch
> when delete index data,throw pool closed in TrackingParallelWriterIndexCommitter class.sql
statement delete from ... for client side, In the case of index table enable,Indexer will
deal index data in server side. Finally server use HTable of index table  which batch mutations. 
> When region split, region close firstly,and then region will close phoenix CP(Indexer)
which call stop method  of Indexer. this method will stop  IndexWriter and IndexBuildManager
,recoveryWriter. But region split failed, start to roll back, which can not processing IndexWriter 
and IndexBuildManager ,recoveryWriter initialization. afterwards deal of index data will
failed which throw pool close.
> A simple test where region split failed, roll back success. but failed to delete index
> 1.create data table and index table
> 2.bulkload data for this table
> 3.alter hbase-server code, which region split throw exception , after region close happen. 
> 4.use hbase shell , split region.
> 5.view regionserver log, where region split failed, and then rollback success.
> 6.user phoenix for delete data, which  will throw exption

This message was sent by Atlassian Jira

View raw message