archive.apache.org does not have a CDN, so it could be slow at times. It is preferable to create our own HDFS namenode and datanode image and test against the latest stable version of Hadoop.
I have disabled the hdfs cluster workflow, let's enable it back when this issue addressed.
FYI: https://hub.docker.com/layers/bde2020/hadoop-namenode/latest/images/sha256-fdf74110805132d646cf6f12635efc0919e1fb2ac5bd376c5366272fc261301e?context=explore
archive.apache.org does not have a CDN, so it could be slow at times. It is preferable to create our own HDFS namenode and datanode image and test against the latest stable version of Hadoop.
I have disabled the hdfs cluster workflow, let's enable it back when this issue addressed.
FYI: https://hub.docker.com/layers/bde2020/hadoop-namenode/latest/images/sha256-fdf74110805132d646cf6f12635efc0919e1fb2ac5bd376c5366272fc261301e?context=explore