I agreed with Andrew too. Users have relied for years on `hadoop classpath`
for their script to launch jobs or other tools, perhaps no the best idea to
change the behavior without providing a proper deprecation path.
thanks!
esteban.
--
Cloudera, Inc.
On Mon, Apr 3, 2017 at 10:26 AM, Andrew Wan
[
https://issues.apache.org/jira/browse/HDFS-8564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esteban Gutierrez resolved HDFS-8564.
-
Resolution: Duplicate
> BlockPoolSlice.checkDirs() will trigger excessive IO wh
, Dmitry Salychev
wrote:
> Hi, Esteban.
>
> Thanks for your reply. Thus, QJM automatic failover option is a cut-edge
> thing. Am I right?
>
> I think that it's a good idea to have truly equal NNs doing their work in
> parallel, as Konstantin Shvachko mentioned.
>
>
&
Hi Dmitry,
Have you looked into the QJM automatic failover mode using the
ZKFailoverController?
https://hadoop.apache.org/docs/r2.6.0/hadoop-project-dist/hadoop-hdfs/HDFSHighAvailabilityWithQJM.html#Automatic_Failover
This is the most commonly used HA mode in production environments. Also
there is
Esteban Gutierrez created HDFS-8564:
---
Summary: BlockPoolSlice.checkDirs() will trigger excessive IO
while traversing all sub-directories under finalizedDir
Key: HDFS-8564
URL: https://issues.apache.org/jira
Esteban Gutierrez created HDFS-8359:
---
Summary: Normalization of timeouts in InputStream and OutputStream
Key: HDFS-8359
URL: https://issues.apache.org/jira/browse/HDFS-8359
Project: Hadoop HDFS
Esteban Gutierrez created HDFS-8311:
---
Summary: DataStreamer.transfer() should timeout the socket
InputStream.
Key: HDFS-8311
URL: https://issues.apache.org/jira/browse/HDFS-8311
Project: Hadoop
