phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Kumar Maturi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5137) Index Rebuild blocks data table region split
Date Wed, 13 Feb 2019 11:43:00 GMT
Kiran Kumar Maturi created PHOENIX-5137:
-------------------------------------------

             Summary: Index Rebuild blocks data table region split
                 Key: PHOENIX-5137
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5137
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.14.1
            Reporter: Kiran Kumar Maturi
            Assignee: Kiran Kumar Maturi


[~lhofhansl] [~vincentpoon] [~tdsilva]

In order to differentiate between the index rebuilder retries  (UngroupedAggregateRegionObserver.rebuildIndices())
and commits that happen in the loop of UngroupedAggregateRegionObserver.doPostScannerOpen()
as part of  PHOENIX-4600 blockingMemstoreSize was set to -1 for rebuildIndices;
{code:java}
commitBatchWithRetries(region, mutations, -1);{code}
blocks the region split as the check for region closing does not happen  blockingMemstoreSize
> 0
{code:java}
for (int i = 0; blockingMemstoreSize > 0 && region.getMemstoreSize() > blockingMemstoreSize
&& i < 30; i++) {
  try{
   checkForRegionClosing();
   ....
{code}
Plan is to have the check for region closing irrespective of the blockingMemstoreSize
{code:java}
int i = 0;
do {
   try {
     if (i > 0) {
         Thread.sleep(100); 
     }
     checkForRegionClosing();   
    } catch (InterruptedException e) {
        Thread.currentThread().interrupt();
        throw new IOException(e);
    }
}while (blockingMemstoreSize > 0 && region.getMemstoreSize() > blockingMemstoreSize
&& i++ < 30);
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message