I would generally design the Guest images to run on local storage, not in a
SAN to decrease load on the network links. The Guest image shouldn't be
very large, anyway.
Data should be stored in the SAN for shared access.
Aside from that, any networking issues as usual depends on the hardware and
your configuration. Maybe you need fatter pipes or more pipes to your SAN,
but if you're currently running multiple Guest images in the SAN that'd
likely be a major load by itself.
Another thing you can do is use a distro/OS with recent architecture. A
couple years ago leading several Linux distros starting moving many of
their mountpoints into tmpfs which means they're running in RAM instead of
hitting your hard drive. In fact, for those OS, if you don't store data in
local storage, after initial boot the disks aren't touched much. Of course,
this won't generally include the "Long Term" distro versions but IMO Java
apps like ES aren't likely subject to changes in the OS outside the JVM.
On Wednesday, February 5, 2014 8:42:43 AM UTC-8, mooky wrote:
I have had a few issues before with linux VM environment (ESX)
- like single points of failure. SAN goes down, you lose all your servers.
- like SAN controller gets saturated, and IOWait on all servers goes
through the roof - everything runs veery slow.
- I have heard other anecdotes regarding networking - and the ESX drivers
not coping under heavy load. We certainly had loads of networking related
problems - that many times we weren't able to get to the bottom - and the
environment support personnel lacked the talent/resources to figure it out
- many many problems due to oversubscription (but thats just down to the
environment being run by muppets).
On Wednesday, 5 February 2014 15:45:09 UTC, Tony Su wrote:
Although I'm running on a different VMware product, I've run other things
than ES on VMware before.
IMO is a good platform, no unusual issues.
Just the usual things...
If the VM was created on a different machine, then you may need to verify
no partition alignment issues.
In my current ES testing, most of my bottlenecks is the disk I/O.
Curiously, Marvel isn't reporting disk usage in the red, but it's obviously
the most loaded of the various resources being used (So, maybe it's not a
real bottleneck?). My current storage is shared SATA/SAS.
Like always, if you're dealing with SSD, about write amplification
and how to deal with it depending on whatever Guest OS you use.
On Wednesday, February 5, 2014 7:22:08 AM UTC-8, mooky wrote:
What's the general opinion about running elasticsearch on VMWare ESX
Are many people running elasticsearch reliably in this kind of env?
Assuming the VM is set up with dedicated/guaranteed mem/cpu, are there
any things to be concerned/worried about?
Disc IO Performance? SAN vs local HDD (local SSD).
Network IO Performance? driver issues ...
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a5ad4e79-5e4b-45d5-9ba5-d3797b3cd5d9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.