Thanks for the quick response Jonathan. Honestly, I am not sure if 2.10.0 will fix my issue but it looks similar to https://issues.apache.org/jira/browse/HDFS-14536 which is not fixed yet so we will probably not see the benefit.
We need to either dig more into the logs and jstack and create a JIRA to see if the developers can comment on what's going on. A datanode restart fixes the latency issue and so it is something that happens over time and need the right instrumentation to figure it out! Thanks, Viral On Thu, Sep 26, 2019 at 6:41 PM Jonathan Hung <jyhung2...@gmail.com> wrote: > Hey Viral, yes. We're working on a 2.10.0 release, I'm the release manager > for that. I can't comment on the particular issue you're seeing, but I plan > to start the release process for 2.10.0 early next week, then 2.10.0 will > be released shortly after that (assuming all goes well). > > Thanks, > Jonathan Hung > > > On Thu, Sep 26, 2019 at 6:34 PM Viral Bajaria <viral.baja...@gmail.com> > wrote: > >> (Cross posting from user list based on feedback by Sean Busbey) >> >> All, >> >> Just saw the announcement for new release for Hadoop 3.2.1, >> congratulations >> team and thanks for all the hard work! >> >> Are we going to see a new release in the 2.x.x ? >> >> I noticed a bunch of tickets that have been resolved in the last year have >> been tagged with 2.10.0 as a fix version and it's been a while since 2.9.2 >> was released so I was wondering if we are going to see a 2.10.0 release >> soon OR should we start looking to upgarde to 3.x line ? >> >> The reason I ask is that we are seeing very high ReadBlockOp Latency on >> our >> datanodes and feel that the issue is due to some locking going on between >> VolumeScanner, DirectoryScanner, RW Block Operations and MetricsRegistry. >> Looking at a few JIRA it looks like 2.10.0 might have some fixes that we >> should try, not fully sure yet! >> >> Thanks, >> Viral >> >
