Hi Daryn,
A slightly related question is that have you used to -refreshCallQueue to tune
config for the fair call queue instead of the normal maintenance(failover +
restart)? If so how is the performance impact?
Thanks,
Fengnan
From: Daryn Sharp
Date: Thursday, November 5, 2020 at 1
Thanks Akira and Sunil for your checks. Will prepare RC2 shortly.
Considering that HDFS-15643 has resolved and committed to 3.2.3, I think we
could backport to 3.2.2. FYI.
Thanks again.
Regards,
He Xiaoqiao
On Fri, Nov 6, 2020 at 10:35 AM Sunil Govindan wrote:
> Thanks Akira. I just saw that th
Thanks Akira. I just saw that the revert of HADOOP-17306 is now pushed to
the 3.2.2 branch as well.
Let's do one more RC. Thanks @Xiaoqiao He for
helping.
Thanks
Sunil
On Fri, Nov 6, 2020 at 6:58 AM Akira Ajisaka wrote:
> -1
>
> - YARN resource localization is broken by HADOOP-17306 and it ha
-1
- YARN resource localization is broken by HADOOP-17306 and it has been
reverted. It should be reverted from 3.2.2 as well. (Thank you Jim
Brennan for the report!)
- Would you include HDFS-15643 in RC2? This fixes checksum error in EC
with ISA-L.
Thank you He Xiaoqiao for preparing the release
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/49/
[Nov 4, 2020 5:53:46 AM] (Xiaoqiao He) HDFS-15651. Client could not obtain
block when DN CommandProcessingThread exit. Contributed by Aiphago.
[Nov 4, 2020 5:12:31 PM] (noreply) HADOOP-17341. Upgrade
Thanks Daryn,
0.01 is just an initial config and it will not exert the penalty to heavy
users. We are doing this to just have the code evaluated but not actually using
the feature.
The blacklist feature is also another thing further in this direction, meaning
heavy users won’t have their c
We're internally running the patch I submitted on HDFS-14403 which was
subsequently modified by other ppl in the community, so it's possible the
community flavor may behave differently. I vaguely remember the RpcMetrics
timeunit was changed from micros to millis. Measuring in millis has
meaningle
Note that I have a Jira up right now for a bug that Daryn found while
testing FCQ internally. Not sure if it is relevant to what you are seeing.
https://issues.apache.org/jira/browse/HADOOP-17342
Jim
On Thu, Nov 5, 2020 at 11:43 AM Fengnan Li wrote:
> Thanks for the response Daryn!
>
>
>
> I ag
Thanks for the response Daryn!
I agree with you that for the overall average qtime it will increase due to the
penalty FCQ brings to the heavy users. However, in our environment, out of the
same consideration I intentionally turned off the Call selection between
queues. i.e. the cost is calc
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/316/
[Nov 4, 2020 3:58:44 AM] (noreply) HDFS-15643. EC: Fix checksum computation in
case of native encoders. (#2424). Contributed by Ayush Saxena.
[Nov 4, 2020 5:53:46 AM] (Xiaoqiao He) HDFS-15651. Client
I submitted the original 2.8 cost-based FCQ patch (thanks to community
members for porting to other branches). We've been running with it since
early 2019 on all clusters. Multiple clusters run at a baseline of ~30k+
ops/sec with some bursting over 100k ops/sec.
If you are looking at the overall
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/107/
No changes
-1 overall
The following subsystems voted -1:
asflicense hadolint jshint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
12 matches
Mail list logo
