You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Graphab offers a kmeans executable to perform clustering, I've tried that on a single node and it works perfectly. My question is, how can I do that in a distributed environment?
I've created two virtual machine, they are on the same network and the ipaddresd of each one is reachable from the other (I've test using ping), each machine has the kmeans executuable compiled from the graphlab source.
I've see in the official documentation that the command for running the kmeans distributed is :
Host file should contain IP addresses of the nodes you intend to form
cluster with.
On Sep 12, 2014 6:27 PM, "Luca Filipponi" notifications@github.com wrote:
Graphab offers a kmeans executable to perform clustering, I've tried that
on a single node and it works perfectly. My question is, how can I do that
in a distributed environment?
I've created two virtual machine, they are on the same network and the
ipaddresd of each one is reachable from the other (I've test using ping),
each machine has the kmeans executuable compiled from the graphlab source.
I've see in the official documentation that the command for running the
kmeans distributed is :
Graphab offers a kmeans executable to perform clustering, I've tried that on a single node and it works perfectly. My question is, how can I do that in a distributed environment?
I've created two virtual machine, they are on the same network and the ipaddresd of each one is reachable from the other (I've test using ping), each machine has the kmeans executuable compiled from the graphlab source.
I've see in the official documentation that the command for running the kmeans distributed is :
mpiexec -n [N machines] --hostfile [host file] ./kmeans ....
How a hostfile should be??
Someone has ever ran kmeans using mpi?
Thanks in advance for the help.
The text was updated successfully, but these errors were encountered: