Sigma-Ma opened a new pull request, #8888:
URL: https://github.com/apache/hbase/pull/8888

   JIRA: https://issues.apache.org/jira/browse/HBASE-30053
   
   ## What changes were proposed in this pull request?
   
   - Reduce the split-test HFile fixture from 9,999,999 rows to 1,000 rows and 
remove the one-byte copy buffer.
   - Copy the configuration before applying export-specific settings.
   - Verify that the snapshot contains two references and produces exactly one 
HFile copy input through the actual InputFormat and RecordReader.
   
   ### Why are the changes needed?
   
   The split test uses a large HFile and a one-byte buffer to expose the 
duplicate-copy race covered by HBASE-28806. This makes the test expensive and 
can exhaust the class-level timeout before cleanup, leaving the mini-cluster 
running when the test is retried.
   
   Checking the copy inputs directly detects duplicate copies 
deterministically, so the regression test no longer needs a large fixture or 
artificially slow copying.
   
   ### How was this patch tested?
   
   ```bash
   mvn-B -ntp -pl hbase-mapreduce -PrunLargeTests 
-Dtest=TestSecureExportFileSystemStateWithMergeOrSplitRegion,TestExportFileSystemStateWithMergeOrSplitRegion,TestExportFileSystemStateWithMergeOrSplitRegionTmpDir
 -Dsurefire.firstPartForkCount=2 -Dsurefire.rerunFailingTestsCount=0 
-Dsurefire.failIfNoSpecifiedTests=true test
   
   # Hadoop 3
   mvn -B -ntp -Dhadoop.profile=3.0 -pl hbase-mapreduce -PrunLargeTests 
-Dtest=TestSecureExportFileSystemStateWithMergeOrSplitRegion,TestExportFileSystemStateWithMergeOrSplitRegion,TestExportFileSystemStateWithMergeOrSplitRegionTmpDir
 -Dsurefire.firstPartForkCount=2 -Dsurefire.rerunFailingTestsCount=0 
-Dsurefire.failIfNoSpecifiedTests=true test
   
   mvn-B -ntp -Dhadoop.profile=3.0 -pl hbase-mapreduce spotless:check
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to