Dear All
Due to our provided not being able / willing to provide is with updates
for the Lustre drivers we are currently stuck with
a 2.6.32 Kernel from 2011 on our 128 Nodes cluster.
Unfortunately, our current setup will not change for the next 18 months or
so until the upgrade has gone on Te
The headnode/childnode issue is usually an architecture mismatch. You can
target a more generic architecture to get around this; see the discussion
in this thread:
https://groups.google.com/d/msg/julia-dev/Eqp0GhZWxME/3mGKX1l_L9gJ
ps: this should go in the FAQ... if someone new on here wants to ma
Elliot and I had some discussions recently where we were thinking it might
be a good idea to combine some of these settings under one easy group flag
like JULIA_PORTABLE=1 or something, that would then set
OPENBLAS_DYNAMIC_ARCH, along with the flags needed for the system image
that I can never
Moritz, I'm interested in what broke on the compute nodes. Do you have any
example output from trying to run Julia on the compute nodes?
-E
On Tue, Oct 28, 2014 at 1:57 PM, Tony Kelman wrote:
> Elliot and I had some discussions recently where we were thinking it might
> be a good idea to combin
Le mardi 28 octobre 2014 à 10:12 -0700, moritz braun a écrit :
> Dear All
>
>
> Due to our provided not being able / willing to provide is with
> updates for the Lustre drivers we are currently stuck with
> a 2.6.32 Kernel from 2011 on our 128 Nodes cluster.
> Unfortunately, our current setup w
Dear Elliot
What happened, is simply a segmentation fault due to libpthread and
thereafter the nodes were not accessible.
regards
Moritz
On Tuesday, 28 October 2014 23:53:03 UTC+2, Elliot Saba wrote:
>
> Moritz, I'm interested in what broke on the compute nodes. Do you have
> any example out
A compatibility/portability flag would be nice. Some cluster architecture have
very little local storage and 3rd party executables are often in an NFS mounted
shared directory.
