[
https://issues.apache.org/jira/browse/HADOOP-18546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645375#comment-17645375
]
ASF GitHub Bot commented on HADOOP-18546:
-----------------------------------------
steveloughran opened a new pull request, #5205:
URL: https://github.com/apache/hadoop/pull/5205
One more followup JIRA based on the experience of trying to work out if a
patched
JAR was being picked up through spark builds.
* ReadBufferManager logs at trace.
* AbfsInputStream.toString() declares fix.
* abfs path capabilities also returns true for the probe "HADOOP-18546".
This allows for programmatic probes in tests.
The cloudstore pathcapabilities command can probe for this; we should move
this into the hadoop cli.
### How was this patch tested?
Currently got spark shell doing repeated validation of 10MB rows; will leave
it running
all night.
Not *yet* run the cloud suites as they stamp on the same container.
I should fix that, really.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> disable purging list of in progress reads in abfs stream closed
> ---------------------------------------------------------------
>
> Key: HADOOP-18546
> URL: https://issues.apache.org/jira/browse/HADOOP-18546
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.3.4
> Reporter: Steve Loughran
> Assignee: Pranav Saxena
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.5
>
>
> turn off the prune of in progress reads in
> ReadBufferManager::purgeBuffersForStream
> this will ensure active prefetches for a closed stream complete. they wiill
> then get to the completed list and hang around until evicted by timeout, but
> at least prefetching will be safe.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
