[HBASE-28953] Prefetch thread shouldn't run for master store

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta-1, 2.7.0, 2.6.1
• Fix Version/s: 3.0.0, 2.7.0, 2.6.2
• Labels: pull-request-available
• Assignee: Wellington Chevreuil
• Reporter: Wellington Chevreuil
• Created: 04/Nov/24 10:43
• Updated: 19/Nov/24 07:49
• Resolved: 18/Nov/24 12:37

Description

The master store is hosted on Master processes. Since masters don't have a BlockCache, we shouldn't run a prefetch thread at all, when opening the master store region.

Currently, this is causing a NoSuchElementException to be logged in master logs, which although harmless, can be confusing for operators:

2024-10-23 15:23:29,236 WARN org.apache.hadoop.hbase.io.hfile.HFileReaderImpl: Prefetch path=s3a://odx-qe-bucket/cc-odx-coy6zg/cod-udzhubgp5l5k/hbase/MasterData/data/master/store/1595e783b53d99cd5eef43b6debb2682/proc/336a510d9f9a472c9e2a8f3e00352e3b, offset=0, end=82012
java.util.NoSuchElementException: No value present
	at java.base/java.util.Optional.get(Optional.java:143)
	at org.apache.hadoop.hbase.io.hfile.HFilePreadReader$1.run(HFilePreadReader.java:73)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecute 

 

 

Issue Links

• links to: GitHub Pull Request #6438
• links to: GitHub Pull Request #6445