We were again hit with a production outage due to DNS dependence within MaxDB. This time we spent 1 day setting up two test servers with Win2K and a third running Linux. All running latest 7.5.0.8.
I reported this problem over a year ago, and no response to my two posts on the topic. http://lists.mysql.com/maxdb/19709 - in reply to my first March 14 2003 posting. Windows ===================== We used Windows 2000 Server with latest service pack and Windows Update. Also tested on Windows XP SP1. -- Win32 version of MaxDB xserver does NOT support the -F parameter! If you run it you get: C:\Program Files\sdb\programs>serv -F No valid option! Use -h to get help. If the remote DNS servers are down (stopped / blocked)... MaxDB will do two nasty things: 1. take 35 seconds to respond to the first SQL from the first client. 2. serialize all other SQL requests... so they won't even START their 35 seconds until the first one completes. Just a matter of time until the server is so backlogged that Extra info: 3. Even on the server itself, "DBMCLI -n localhost" will fail to respond when DNS is unavailable. 4. As soon as DNS is restored, all returns to normal resuming right where it halted. Linux ====== So we setup a Redhat 9 system and installed MaxDB. We found if the DNS server is down (stopped / blocked); 1. maxDB takes 20 seconds to respond 2. Adding the -F parameter to XServer fixes this! So where is the -F parameter for Windows?! Stephen Gutknecht full time traveler, home on wheels currently in Grand Prairie, Texas USA -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
