[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867426#comment-17867426
]
Viraj Jasani commented on HADOOP-19218:
---
Please review
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867232#comment-17867232
]
Viraj Jasani edited comment on HADOOP-19218 at 7/19/24 8:10 AM:
yeah i
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867232#comment-17867232
]
Viraj Jasani edited comment on HADOOP-19218 at 7/19/24 8:08 AM:
yeah i
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867232#comment-17867232
]
Viraj Jasani commented on HADOOP-19218:
---
yeah i am also bit confused, i can create addendum PR
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867231#comment-17867231
]
Viraj Jasani commented on HADOOP-19218:
---
Anyway, if we want to keep (host + ip) format (available
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867222#comment-17867222
]
Viraj Jasani commented on HADOOP-19218:
---
For TestFSNamesystemLockReport, yes it is broken by this
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867077#comment-17867077
]
Viraj Jasani commented on HADOOP-19218:
---
Thank you once again!
> Avoid DNS lookup while creating
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866882#comment-17866882
]
Viraj Jasani edited comment on HADOOP-19218 at 7/17/24 11:50 PM:
-
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866882#comment-17866882
]
Viraj Jasani commented on HADOOP-19218:
---
Thanks for the reviews [~shahrs87] [~dmanning]
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19218:
--
Component/s: ipc
> Avoid DNS lookup while creating IPC Connection object
>
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862591#comment-17862591
]
Viraj Jasani commented on HADOOP-19218:
---
FYI [~UselessCoder] [~dmanning] [~shahrs87] [~apurtell]
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862579#comment-17862579
]
Viraj Jasani commented on HADOOP-19218:
---
Thread dump ref:
{code:java}
"IPC Server listener on
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19218:
--
Description:
Been running HADOOP-18628 in production for quite sometime, everything works
[
https://issues.apache.org/jira/browse/HADOOP-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19218:
-
Assignee: Viraj Jasani
> Avoid DNS lookup while creating IPC Connection object
>
Viraj Jasani created HADOOP-19218:
-
Summary: Avoid DNS lookup while creating IPC Connection object
Key: HADOOP-19218
URL: https://issues.apache.org/jira/browse/HADOOP-19218
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853327#comment-17853327
]
Viraj Jasani commented on HADOOP-19197:
---
Amazing, will take a look. Thanks for working on this!
[
https://issues.apache.org/jira/browse/HADOOP-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19197:
-
Assignee: (was: Viraj Jasani)
> S3A: Support AWS KMS Encryption Context
>
[
https://issues.apache.org/jira/browse/HADOOP-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19197:
-
Assignee: Viraj Jasani
> S3A: Support AWS KMS Encryption Context
>
[
https://issues.apache.org/jira/browse/HADOOP-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853304#comment-17853304
]
Viraj Jasani commented on HADOOP-19197:
---
How about we allow user to configure
[
https://issues.apache.org/jira/browse/HADOOP-19197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853016#comment-17853016
]
Viraj Jasani commented on HADOOP-19197:
---
We need to use it at 3 places: CopyObjectRequest,
[
https://issues.apache.org/jira/browse/HADOOP-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846806#comment-17846806
]
Viraj Jasani commented on HADOOP-19148:
---
Build is fine, dependency tree looks good (except it has
[
https://issues.apache.org/jira/browse/HADOOP-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846458#comment-17846458
]
Viraj Jasani commented on HADOOP-19148:
---
[~brahmareddy] is anyone picking this up? If not, let me
[
https://issues.apache.org/jira/browse/HADOOP-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19146:
--
Component/s: test
> noaa-cors-pds bucket access with global endpoint fails
>
Viraj Jasani created HADOOP-19146:
-
Summary: noaa-cors-pds bucket access with global endpoint fails
Key: HADOOP-19146
URL: https://issues.apache.org/jira/browse/HADOOP-19146
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19146:
-
Assignee: Viraj Jasani
> noaa-cors-pds bucket access with global endpoint fails
>
[
https://issues.apache.org/jira/browse/HADOOP-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825912#comment-17825912
]
Viraj Jasani commented on HADOOP-19066:
---
Addendum PR:
[
https://issues.apache.org/jira/browse/HADOOP-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816513#comment-17816513
]
Viraj Jasani commented on HADOOP-18980:
---
Addressed edge cases with addendum PR:
[
https://issues.apache.org/jira/browse/HADOOP-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19066:
--
Status: Patch Available (was: In Progress)
> AWS SDK V2 - Enabling FIPS should be allowed
[
https://issues.apache.org/jira/browse/HADOOP-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19072:
-
Assignee: Viraj Jasani
> S3A: expand optimisations on stores with
[
https://issues.apache.org/jira/browse/HADOOP-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815822#comment-17815822
]
Viraj Jasani commented on HADOOP-19072:
---
The improvement makes sense, as long as downstreamer
[
https://issues.apache.org/jira/browse/HADOOP-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814576#comment-17814576
]
Viraj Jasani commented on HADOOP-19066:
---
Indeed! hopefully some final stabilization work.
> AWS
[
https://issues.apache.org/jira/browse/HADOOP-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814171#comment-17814171
]
Viraj Jasani commented on HADOOP-19066:
---
Will run the whole suite with FIPS support + central
[
https://issues.apache.org/jira/browse/HADOOP-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19066:
-
Assignee: Viraj Jasani
> AWS SDK V2 - Enabling FIPS should be allowed with central
Viraj Jasani created HADOOP-19066:
-
Summary: AWS SDK V2 - Enabling FIPS should be allowed with central
endpoint
Key: HADOOP-19066
URL: https://issues.apache.org/jira/browse/HADOOP-19066
Project:
[
https://issues.apache.org/jira/browse/HADOOP-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17812142#comment-17812142
]
Viraj Jasani commented on HADOOP-19022:
---
It's fine [~ste...@apache.org], i anyways need to make
[
https://issues.apache.org/jira/browse/HADOOP-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809636#comment-17809636
]
Viraj Jasani commented on HADOOP-18975:
---
{quote}you must have set a global endpoint, rather than
[
https://issues.apache.org/jira/browse/HADOOP-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809271#comment-17809271
]
Viraj Jasani edited comment on HADOOP-18975 at 1/22/24 7:33 AM:
[
https://issues.apache.org/jira/browse/HADOOP-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809271#comment-17809271
]
Viraj Jasani commented on HADOOP-18975:
---
{code:java}
[
https://issues.apache.org/jira/browse/HADOOP-19044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-19044:
-
Assignee: Viraj Jasani
> AWS SDK V2 - Update S3A region logic
>
[
https://issues.apache.org/jira/browse/HADOOP-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804132#comment-17804132
]
Viraj Jasani commented on HADOOP-19023:
---
{quote} * make sure you've not got a site config with an
[
https://issues.apache.org/jira/browse/HADOOP-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804129#comment-17804129
]
Viraj Jasani commented on HADOOP-19022:
---
{quote}have you explicitly set it in your site config?
[
https://issues.apache.org/jira/browse/HADOOP-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19023:
--
Component/s: test
> ITestS3AConcurrentOps#testParallelRename intermittent timeout failure
>
[
https://issues.apache.org/jira/browse/HADOOP-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19022:
--
Summary: S3A : ITestS3AConfiguration#testRequestTimeout failure (was:
[
https://issues.apache.org/jira/browse/HADOOP-19023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-19023:
--
Summary: S3A : ITestS3AConcurrentOps#testParallelRename intermittent
timeout failure (was:
[
https://issues.apache.org/jira/browse/HADOOP-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18980:
--
Status: Patch Available (was: In Progress)
> S3A credential provider remapping: make
[
https://issues.apache.org/jira/browse/HADOOP-18959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803401#comment-17803401
]
Viraj Jasani commented on HADOOP-18959:
---
[~slfan1989] this is already committed to trunk, only
Viraj Jasani created HADOOP-19023:
-
Summary: ITestS3AConcurrentOps#testParallelRename intermittent
timeout failure
Key: HADOOP-19023
URL: https://issues.apache.org/jira/browse/HADOOP-19023
Project:
[
https://issues.apache.org/jira/browse/HADOOP-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802395#comment-17802395
]
Viraj Jasani commented on HADOOP-19022:
---
It's small test, but perhaps good to cover both cases:
Viraj Jasani created HADOOP-19022:
-
Summary: ITestS3AConfiguration#testRequestTimeout failure
Key: HADOOP-19022
URL: https://issues.apache.org/jira/browse/HADOOP-19022
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790816#comment-17790816
]
Viraj Jasani commented on HADOOP-18991:
---
As per HADOOP-16542, if we remove this, hive build
[
https://issues.apache.org/jira/browse/HADOOP-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790788#comment-17790788
]
Viraj Jasani commented on HADOOP-18991:
---
[~stoty] is this the cause for managing it in phoenix
[
https://issues.apache.org/jira/browse/HADOOP-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788128#comment-17788128
]
Viraj Jasani commented on HADOOP-18980:
---
{quote}exactly; though i'd expect the remapping to be
[
https://issues.apache.org/jira/browse/HADOOP-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788128#comment-17788128
]
Viraj Jasani edited comment on HADOOP-18980 at 11/20/23 6:44 PM:
-
In
[
https://issues.apache.org/jira/browse/HADOOP-18980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787854#comment-17787854
]
Viraj Jasani commented on HADOOP-18980:
---
Something like this maybe?
{code:java}
[
https://issues.apache.org/jira/browse/HADOOP-18959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18959:
-
Assignee: Viraj Jasani
> Use builder for prefetch CachingBlockManager
>
Viraj Jasani created HADOOP-18959:
-
Summary: Use builder for prefetch CachingBlockManager
Key: HADOOP-18959
URL: https://issues.apache.org/jira/browse/HADOOP-18959
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18918:
--
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
Status:
[
https://issues.apache.org/jira/browse/HADOOP-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780014#comment-17780014
]
Viraj Jasani commented on HADOOP-18952:
---
This has been the case since the beginning:
Stat:
[
https://issues.apache.org/jira/browse/HADOOP-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HADOOP-18829.
---
Fix Version/s: 3.4.0
3.3.9
Hadoop Flags: Reviewed
[
https://issues.apache.org/jira/browse/HADOOP-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776356#comment-17776356
]
Viraj Jasani edited comment on HADOOP-18931 at 10/17/23 7:16 PM:
-
[
https://issues.apache.org/jira/browse/HADOOP-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776356#comment-17776356
]
Viraj Jasani commented on HADOOP-18931:
---
sounds good, it makes sense to log for all fs invocation
[
https://issues.apache.org/jira/browse/HADOOP-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18918:
--
Status: Patch Available (was: In Progress)
> ITestS3GuardTool fails if SSE/DSSE encryption
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18850:
--
Status: Patch Available (was: In Progress)
> Enable dual-layer server-side encryption with
[
https://issues.apache.org/jira/browse/HADOOP-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775281#comment-17775281
]
Viraj Jasani commented on HADOOP-18931:
---
i thought we were already logging it during the first
[
https://issues.apache.org/jira/browse/HADOOP-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18918:
--
Summary: ITestS3GuardTool fails if SSE/DSSE encryption is used (was:
ITestS3GuardTool fails
[
https://issues.apache.org/jira/browse/HADOOP-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18918:
--
Priority: Minor (was: Major)
> ITestS3GuardTool fails if SSE encryption is used
>
[
https://issues.apache.org/jira/browse/HADOOP-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18918:
-
Assignee: Viraj Jasani
> ITestS3GuardTool fails if SSE encryption is used
>
Viraj Jasani created HADOOP-18918:
-
Summary: ITestS3GuardTool fails if SSE encryption is used
Key: HADOOP-18918
URL: https://issues.apache.org/jira/browse/HADOOP-18918
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18850:
-
Assignee: Viraj Jasani
> Enable dual-layer server-side encryption with AWS KMS keys
[
https://issues.apache.org/jira/browse/HADOOP-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770745#comment-17770745
]
Viraj Jasani commented on HADOOP-18915:
---
Nice find!
> HTTP timeouts are not set correctly
>
[
https://issues.apache.org/jira/browse/HADOOP-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18208:
-
Assignee: (was: Viraj Jasani)
> Remove all the log4j reference in modules other
[
https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-16206:
-
Assignee: (was: Viraj Jasani)
> Migrate from Log4j1 to Log4j2
>
[
https://issues.apache.org/jira/browse/HADOOP-18207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18207:
-
Assignee: (was: Viraj Jasani)
> Introduce hadoop-logging module
>
[
https://issues.apache.org/jira/browse/HADOOP-15984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-15984:
-
Assignee: (was: Viraj Jasani)
> Update jersey from 1.19 to 2.x
>
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755406#comment-17755406
]
Viraj Jasani commented on HADOOP-18850:
---
[~ste...@apache.org] are you in favor of this before v2
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755394#comment-17755394
]
Viraj Jasani commented on HADOOP-18850:
---
only recently HADOOP-18832 bumped sdk bundle to
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755392#comment-17755392
]
Viraj Jasani edited comment on HADOOP-18850 at 8/17/23 7:13 AM:
it
[
https://issues.apache.org/jira/browse/HADOOP-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755392#comment-17755392
]
Viraj Jasani commented on HADOOP-18850:
---
SSEAlgorithm added DSSE as part of 1.12.488 release:
[
https://issues.apache.org/jira/browse/HADOOP-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755385#comment-17755385
]
Viraj Jasani commented on HADOOP-18852:
---
{quote}for other reads, we may want a bigger prefech
[
https://issues.apache.org/jira/browse/HADOOP-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755384#comment-17755384
]
Viraj Jasani commented on HADOOP-18852:
---
{quote}also, if a read is in a block other than the
[
https://issues.apache.org/jira/browse/HADOOP-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750035#comment-17750035
]
Viraj Jasani commented on HADOOP-18829:
---
sure thing, i think this can wait for sure. thanks
>
[
https://issues.apache.org/jira/browse/HADOOP-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748981#comment-17748981
]
Viraj Jasani commented on HADOOP-18832:
---
ITestS3AFileContextStatistics#testStatistics is flaky:
[
https://issues.apache.org/jira/browse/HADOOP-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748980#comment-17748980
]
Viraj Jasani commented on HADOOP-18832:
---
Testing in progress: Test results look good with -scale
[
https://issues.apache.org/jira/browse/HADOOP-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18832:
--
Description: aws sdk versions < 1.12.499 uses a vulnerable version of netty
and hence
[
https://issues.apache.org/jira/browse/HADOOP-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18832:
-
Assignee: Viraj Jasani
> Upgrade aws-java-sdk to 1.12.499+
>
Viraj Jasani created HADOOP-18832:
-
Summary: Upgrade aws-java-sdk to 1.12.499+
Key: HADOOP-18832
URL: https://issues.apache.org/jira/browse/HADOOP-18832
Project: Hadoop Common
Issue Type:
Viraj Jasani created HADOOP-18829:
-
Summary: s3a prefetch LRU cache eviction metric
Key: HADOOP-18829
URL: https://issues.apache.org/jira/browse/HADOOP-18829
Project: Hadoop Common
Issue
Viraj Jasani created HADOOP-18809:
-
Summary: s3a prefetch read/write file operations should guard
channel close
Key: HADOOP-18809
URL: https://issues.apache.org/jira/browse/HADOOP-18809
Project:
[
https://issues.apache.org/jira/browse/HADOOP-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743344#comment-17743344
]
Viraj Jasani edited comment on HADOOP-18805 at 7/17/23 8:15 PM:
sorry
[
https://issues.apache.org/jira/browse/HADOOP-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743344#comment-17743344
]
Viraj Jasani edited comment on HADOOP-18805 at 7/15/23 6:48 AM:
sorry
[
https://issues.apache.org/jira/browse/HADOOP-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17743344#comment-17743344
]
Viraj Jasani commented on HADOOP-18805:
---
sorry Steve, i was not aware you already created this
[
https://issues.apache.org/jira/browse/HADOOP-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18805:
-
Assignee: (was: Viraj Jasani)
> s3a large file prefetch tests are too slow, don't
[
https://issues.apache.org/jira/browse/HADOOP-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18805:
-
Assignee: Viraj Jasani
> s3a large file prefetch tests are too slow, don't validate
[
https://issues.apache.org/jira/browse/HADOOP-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742667#comment-17742667
]
Viraj Jasani commented on HADOOP-18791:
---
sounds good, i just realized unbuffer is already
[
https://issues.apache.org/jira/browse/HADOOP-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18791:
-
Assignee: (was: Viraj Jasani)
> S3A prefetching: switch to prefetching for chosen
[
https://issues.apache.org/jira/browse/HADOOP-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned HADOOP-18791:
-
Assignee: Viraj Jasani
> S3A prefetching: switch to prefetching for chosen read
[
https://issues.apache.org/jira/browse/HADOOP-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738379#comment-17738379
]
Viraj Jasani commented on HADOOP-18291:
---
[~ste...@apache.org] if you have bandwidth to review:
[
https://issues.apache.org/jira/browse/HADOOP-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HADOOP-18291:
--
Status: Patch Available (was: In Progress)
> S3A prefetch - Implement LRU cache for
[
https://issues.apache.org/jira/browse/HADOOP-18756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737387#comment-17737387
]
Viraj Jasani commented on HADOOP-18756:
---
Steve, could you please help close this Jira? am i
[
https://issues.apache.org/jira/browse/HADOOP-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735343#comment-17735343
]
Viraj Jasani commented on HADOOP-18777:
---
please take a look at the discussion on HADOOP-18033
>
1 - 100 of 649 matches
Mail list logo
