[
https://issues.apache.org/jira/browse/HDFS-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010479#comment-17010479
]
Rakesh Radhakrishnan commented on HDFS-15080:
---------------------------------------------
Thanks [~PhiloHe], its good finding. +1 patch looks good to me. I will commit
this shortly to the branches.
Since this is related to the Pmem native bindings, excluding unit test case for
this change.
> Fix the issue in reading persistent memory cache with an offset
> ---------------------------------------------------------------
>
> Key: HDFS-15080
> URL: https://issues.apache.org/jira/browse/HDFS-15080
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: caching, datanode
> Reporter: Feilong He
> Assignee: Feilong He
> Priority: Major
> Fix For: 3.3.0, 3.1.4, 3.2.2
>
> Attachments: HDFS-15080-000.patch, HDFS-15080-branch-3.1-000.patch,
> HDFS-15080-branch-3.2-000.patch
>
>
> Some applications can read a segment of pmem cache with an offset specified.
> The previous implementation for pmem cache read with DirectByteBuffer didn't
> cover this situation.
> Let me explain further. In our test, we used spark SQL to run some TPC-DS
> workload to read the cache data and hits read exception. This was due to the
> missed seek offset arg, which is used in spark SQL to read data packet by
> packet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
