On Wed, 17 Sep 2014 at 18:12 -0000, Christopher Samuel wrote:
> On 18/09/14 03:08, Stuart Barkley wrote:
>
> > Any thoughts on why we might still be seeing this set to 1 on our
> > diskless systems? So far I have not found any references to this
> > variable in our startup other than the commented out xCAT one.
>
> FWIW our statelite nodes running RHEL 6.4 (6.5 upgrade scheduled for
> October) have that value at 0, we're running xCAT 2.8.3. We're not
> setting it anywhere we're aware of.
>
> What's the kernel running on the compute nodes?
Chris, I remember your cluster was similar to ours, except bigger and
newer. Are you running M3 or M4 systems?
We are now running kernel-2.6.32-431.23.3.el6.x86_64 on all of our
compute nodes (CentOS and EPEL mirrored as of 20140830).
<sidetrack>
Our CentOS 6.5 rollout has been a little less successful than I had
hopped. The first compute image had a kernel performance regression
and we needed to revert to the last 6.4 kernel (keeping the rest of
6.5). Our current 'stable' version has a regression in the EPEL
version of R (or maybe just an annoying to users change "libRblas").
The real annoyance I find is the GPFS kernel module rebuild needed if
our 'stable' freeze includes a kernel change.
</sidetrack>
One of the things I needed to do was a more complete inventory of the
situation across our various systems. I've now looked in more detail
at our support and lab systems including another cluster we are
working on. The results are interesting, but not xCAT related.
All of our IBM x3650 M2, x3650 M3, dx360 M2 have zone_reclaim_mode set
to 1. Some of these are running CentOS 6.4 from over a year ago.
This includes several systems installed from CD/USB/Kickstart.
One odd ball homebrew lab system also has zone_reclaim_mode set to 1.
All of the other systems I can see have zone_reclaim_mode set to 0.
This includes VMs (running under KVM), other homebrew systems, and a
handful of systems from other vendors.
Also of note, all our newer IBM systems have zone_reclaim_mode set to
0. This includes x3650 M4, dx360 M4, x3690 X5 and x3850 X5 systems (a
small 'new' cluster, a GSS rack, some high memory compute nodes and
some other miscellaneous gear).
It may also be time for us to review our BIOS/IMM versions and even
our changes from the defaults. Lots to do.
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
