ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

System requirements for WebManager MobileNumber555657585960616263646566Version (indetail) Upgraded section Cause3.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-1If an I/O error occurred on a server, The remaining disk error flag wasand a disk error flag remains on the not properly dealt with.cluster partition, the server isrestarted repeatedly if the CPU isrestarted without replacing the disk.In an x86_64 environment in which an A stack was destroyed whileI/O error occurred on the mirror disk, performing reset processing.panic is performed rather than reset.When an asynchronous mode mirror The data transmission processingon a VMware guest OS is used and delay was not properly dealt with.ACK timeout is set to less than 30seconds, 100% of CPU usage is theVMware task, and the OS stalls.When an asynchronous mode mirror Cases exist in which processingon a VMware guest OS is used, the which should not be in reverse ofserver caused PANIC while writing in the original processing order is inan environment running multiple reverse order due to the order of theguest OSes, each of which is VMware CPU switch.assigned only one CPU.If, in the first cluster configuration, the Return value determination of theenvironment consisted of 3 or more license collection processing wasnodes and the CPU licenses were incorrect.only registered to a single server,sometimes license authenticationfailed and the CPU could not start.If there was a group whose failover Startup processing on anotherattribute set to “Dynamic failover”, all server was executed at the samegroups take longer to startup. time.When stopping a monitor resource There was a flaw in the processingwhich is being continuously that terminates the child processesmonitored, Application Server Agent of the Application Server Agent.sometimes terminated otherprocesses when it was stopped.Monitor status changed to a status Sometimes the status wasother than “suspend” after overwritten after it was set tosuspending the monitor resource. suspend.When a monitor resource is Depending on timing, waitpid()suspended, it sometimes remained was not executed when childas a zombie process.processes were terminated.When using diverse resources or The initialized area that managesmonitors, if the number of the types is only for use with 128ExpressCluster module types that types.output logs exceeds 128, sometimesinternal logs are not output.MA memory leak occurred when Internal information was notsuspending a cluster failed because a discarded at the time of the failure togroup was moving.suspend the cluster.A memory leak occurred when Internal information was notstopping a cluster failed because a discarded at the time of the failure togroup was moving.stop the cluster.Section II Installing ExpressCluster91