Steve Loughran

please, avoid force push unless things are completely unreconcilable *or nobody has reviewed yet*. It really makes reviewing harder, which discourages people from reviewing.

the checkstyle is because it wants `./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/hdfs/protocol/datatransfer/` to have a package class describing it proposed * add one * tag stability as stable * tag scope as LimitedPrivate("yarn") * mention...

let's see what happens this time. I don't normally trigger the hdfs/yarn tests, and when I do there are often some which are a bit brittle to: native io thread...

FYI, Jira on create performance. I'm worrying about how to remove/delay client configuration, so adding a new client makes things way worse: HADOOP-19205

It's still happening in FileSystem.initialize(). If I get time this week I'll do my PoC of lazy creation of transfer manager and async client, as that's doubled startup time already....

#6892 is the draft pr with lazy creation; a new s3 client would go in there, but ideally we'd actually push the listing/transformation code into S3AStore so the extra client...

exactly. when its not needed: no penalty.

@shameersss1 unless you have no choice, please try not to rebase and force push prs once reviews have started. makes it a lot harder to see what has changed

@shameersss1 what do you think of @raphaelazzolini 's comment

@shameersss1 I'm not going to be reviewing anything until that hadoop 3.4.1 release is out. Sorry. When I do start reviewing stuff I am likely to start with those by...