H13-711_V3.5 · Question #394
The index data of ElasticSearch can only be saved in the HDFS system.
The correct answer is B. False. B is correct because Elasticsearch stores its index data locally on the node's filesystem (typically on disk using Lucene segment files), and it supports multiple storage backends - including local disk, network-attached storage, cloud object stores (S3, GCS, Azure), and shared…
Question
The index data of ElasticSearch can only be saved in the HDFS system.
Options
- ATrue
- BFalse
How the community answered
(34 responses)- A21% (7)
- B79% (27)
Explanation
B is correct because Elasticsearch stores its index data locally on the node's filesystem (typically on disk using Lucene segment files), and it supports multiple storage backends - including local disk, network-attached storage, cloud object stores (S3, GCS, Azure), and shared file systems. HDFS is not required and is not even Elasticsearch's native storage layer.
Why A is wrong: Restricting Elasticsearch to HDFS would contradict its design as a distributed, standalone search engine. Elasticsearch manages its own distributed data storage and replication without depending on Hadoop's ecosystem at all - you can run it entirely without Hadoop.
Memory tip: Think of Elasticsearch as self-sufficient - it has its own distributed storage and replication built in (primary/replica shards), so it doesn't need to "borrow" HDFS from Hadoop. If you remember that Elasticsearch is not part of the Hadoop ecosystem, you'll avoid this trap.
Topics
Community Discussion
No community discussion yet for this question.