Hello, HDFS client CLI is not the only way to access data in a distributed storage.
In this video I will show you several more popular approaches.
to get information about that configure data analysis and available capacity.
By default, this UI is available on a name note cost on 50070 port.
it's size and generation temp and replicas locations.
you can also see block pool ID.
of a number of notes, you should also distribute meta information.
This functionality is possible by HDFS Federation installation.
In this case, there will be several name nodes.
All of them they will be independent from each other.
by physical ability and reliability this way.
In short, less troubles for you.
WebUI is a read-only HTTP API.
then you should definitely take a look at WebHDFS.
It provides HTTP rest API throughout two types of installations.
with HDFS proxies which will translate your queries into RPC codes.
Let us dive deep to this protocol and see how to read a file content.
First of all you need to request replica locations from name node.
automate different HTTP query related tasks.
When you use -i flag, you see http headers in the output.
I was redirected to a data node to read data from.
I insist you try it.
because it will be a home task, and next class we'll start from checking it.
get the file data from the provided HTTP location.
protocol power and ask a curl to follow redirects automatically.
You only need to supply minus capital to the first comment.
you to get different slices of a file.
With HTTP GET requests, you usually operate with name node.
of a file system three, and to add new content to a distributed storage.
curiosity about API operations and usage examples.
you should know how web UI looks like and how to locate file blocks locations.
You should be able to operate HDFS via curl request.
append to the file, change replication factor, and so on.