You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chao Wang (Jira)" <ji...@apache.org> on 2020/04/21 06:45:00 UTC
[jira] [Created] (PHOENIX-5861) Delete index data failed,due to
pool closed
Chao Wang created PHOENIX-5861:
----------------------------------
Summary: Delete index data failed,due to pool closed
Key: PHOENIX-5861
URL: https://issues.apache.org/jira/browse/PHOENIX-5861
Project: Phoenix
Issue Type: Bug
Components: core
Affects Versions: 4.13.1
Reporter: Chao Wang
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 data.
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 sqlline.py for delete data, which will throw exption
--
This message was sent by Atlassian Jira
(v8.3.4#803005)