You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:20:07 UTC

[jira] [Created] (TRAFODION-1125) LP Bug: 1439421 - HBase-trx TrxRegionEndpoint starts a transaction for a performScan operation on a scanner that has already been closed

Alice Chen created TRAFODION-1125:
-------------------------------------

             Summary: LP Bug: 1439421 - HBase-trx TrxRegionEndpoint starts a transaction for a performScan operation on a scanner that has already been closed
                 Key: TRAFODION-1125
                 URL: https://issues.apache.org/jira/browse/TRAFODION-1125
             Project: Apache Trafodion
          Issue Type: Bug
            Reporter: Joanie Cooper
            Assignee: Joanie Cooper
            Priority: Critical


A TrxRegionEndpoint "performScan" protobuf call is received after a previous open scanner has been closed and the transaction identifier has been retired.  The subsequent"performScan" operation is for the same region that has successfully completed a full protocol series of a TrxRegion "openScanner/performScan/closeScanner" protobuf operations and have retired the transaction.

As the transaction has been retired, the TrxRegionEndpoint coprocessor will create a new transactionState object and try to find a scanner object.

As the previous scanner has been closed, a null is returned.

Previously, we were also on a higher scanner number, e.g. 23 for this table.
The performScan is attempting a scan operation on a scanner with a scanner id  of “0”.
 
hbase-cmf-hbase-REGIONSERVER-centos-ah2.hpl.hp.com.log.out:2015-03-09 09:29:21,434 TRACE org.apache.hadoop.hbase.coprocessor.transactional.TrxRegionEndpoint: TrxRegionEndpoint coprocessor: performScan - txId 136052, scanner id 0, numberOfRows 2614, nextCallSeq 0, closeScanner is false, region is TRAFODION.BENCH56.OE_ORDERLINE_12,\x00\x00\x00\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00,1425744440518.c435085cabe98dbb4e31420a47ad95c4.
 
hbase-cmf-hbase-REGIONSERVER-centos-ah2.hpl.hp.com.log.out:2015-03-09 09:29:21,434 TRACE org.apache.hadoop.hbase.coprocessor.transactional.TrxRegionEndpoint: TrxRegionEndpoint coprocessor: performScan - txId 136052, performScan rsh is null, UnknownScannerException for scannerId: 0, nextCallSeq was 1, for region TRAFODION.BENCH56.OE_ORDERLINE_12,\x00\x00\x00\x05\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00,1425744440518.c435085cabe98dbb4e31420a47ad95c4


The client does receive the "performScan" -8448 error for the query.  

We should be able to determine that we have successfully sent all rows for the scan and not allow asubsequent "performScan" to start a new transaction state object in the TrxRegionEndpoint coprocess that errors out immediately.

Analysis is being done to determine why the additional "performScan" is being sent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)