Let me pose a question by suggesting two extremes for hardware to create
and maintain a growing ElasticSearch cluster datacenter (not in the cloud).
One extreme places redundancy at the server hardware level, by which I mean:
dual power supplies, RAID hard drives
Another extreme places redundancy in a multitude of backup servers:
commodity servers, single power supply, no RAID on the disks, low cost,
with a cluster monitor that can advise of a failed master or backup, and
can rebuild the replacement
I would love to learn how others see or implement within the boundaries of
those extremes, with the understanding that the two poles are just
suggestions, there may be other ways to slice this space.
Many thanks in advance
Jack
ps: documents I read based on a broad query:
Personally, I'd go with the latter and then let the software handle all the
redundancy. You can get super cheap 1RU pizza boxes from Quanta or the like
and save yourself a bundle in that area and then leverage automation and
configuration using The Foreman and Puppet.
Tie a bit more smarts into it and you would have an awesome elastic compute
platform. Or just use something like OpenStack, though it might be a bit
heavy.
Let me pose a question by suggesting two extremes for hardware to create
and maintain a growing Elasticsearch cluster datacenter (not in the cloud).
One extreme places redundancy at the server hardware level, by which I
mean:
dual power supplies, RAID hard drives
Another extreme places redundancy in a multitude of backup servers:
commodity servers, single power supply, no RAID on the disks, low cost,
with a cluster monitor that can advise of a failed master or backup, and
can rebuild the replacement
I would love to learn how others see or implement within the boundaries of
those extremes, with the understanding that the two poles are just
suggestions, there may be other ways to slice this space.
Personally, I'd go with the latter and then let the software handle all
the redundancy. You can get super cheap 1RU pizza boxes from Quanta or the
like and save yourself a bundle in that area and then leverage automation
and configuration using The Foreman and Puppet.
Tie a bit more smarts into it and you would have an awesome elastic
compute platform. Or just use something like OpenStack, though it might be
a bit heavy.
Let me pose a question by suggesting two extremes for hardware to create
and maintain a growing Elasticsearch cluster datacenter (not in the cloud).
One extreme places redundancy at the server hardware level, by which I
mean:
dual power supplies, RAID hard drives
Another extreme places redundancy in a multitude of backup servers:
commodity servers, single power supply, no RAID on the disks, low cost,
with a cluster monitor that can advise of a failed master or backup, and
can rebuild the replacement
I would love to learn how others see or implement within the boundaries
of those extremes, with the understanding that the two poles are just
suggestions, there may be other ways to slice this space.
Personally, I'd go with the latter and then let the software handle all
the redundancy. You can get super cheap 1RU pizza boxes from Quanta or the
like and save yourself a bundle in that area and then leverage automation
and configuration using The Foreman and Puppet.
Tie a bit more smarts into it and you would have an awesome elastic
compute platform. Or just use something like OpenStack, though it might be
a bit heavy.
Let me pose a question by suggesting two extremes for hardware to create
and maintain a growing Elasticsearch cluster datacenter (not in the cloud).
One extreme places redundancy at the server hardware level, by which I
mean:
dual power supplies, RAID hard drives
Another extreme places redundancy in a multitude of backup servers:
commodity servers, single power supply, no RAID on the disks, low cost,
with a cluster monitor that can advise of a failed master or backup, and
can rebuild the replacement
I would love to learn how others see or implement within the boundaries
of those extremes, with the understanding that the two poles are just
suggestions, there may be other ways to slice this space.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.