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
