Thanks! Unfortunately precreatemypostscripts also has a bug
I have reported that causes them to not work properly, so that's
also not a great option for us. (Email subject for bug report:
precreatemypostscripts file, /tftpboot/mypostscripts, not always
getting rewritten as expected). If setting nodestatus to 0 resolves
the majority of the performance problems we'll go that route.
Looking forward to the next release of xCAT that has all these bugs
fixed! :-)
On 3/2/2014 8:59 PM, Xiao Peng Wang
wrote:
I cannot see any impact except
the status of node won't be update when setting
'site.nodestatus=n', you can try to leverage it to solve your
issue.
But I am thinking maybe your
issue caused by the running of 'getpostscripts' when booting
the diskless nodes. You can try to set the
site.precreatemypostscripts=1 to improve the performance of
getmypostscript operation.
I suggest you to try them one
by one and then both to see the result.
Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: w...@cn.ibm.com
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West
Road, Haidian District Beijing P.R.China 100193
 Russell Jones
---2014/03/02 13:18:43---Hi all, We are seeing pretty
consistently that when 50+ diskless nodes are
From: Russell Jones
<russell-l...@jonesmail.me>
To: xcat-user@lists.sourceforge.net,
Date: 2014/03/02 13:18
Subject: [xcat-user] Additional performance
issues
Hi all,
We are seeing pretty consistently that when 50+ diskless nodes
are
booted against the same single service node, before showing
their login
console they all hang for around 5-10 minutes after
postscripts run
while the service node is chugging away at using a constant
100% of a
single core. The process on the service node that is at fault
is the
"install monitor".
This seems to be tied to the site.nodestatus option. Other
than
disabling this option (and fixing the diskfull reinstall loop
bug with
it that I reported earlier), is there a way of improving the
responsiveness of a service node when it's updating the node's
status?
Would we lose anything from disabling this option besides the
"status"
column not being updated?
Thanks!
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco
certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow
Analyzer
Customize your own dashboards, set traffic alerts and generate
reports.
Network behavioral analysis & security monitoring.
All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
|
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
