Windows server restricts max_open_files to 2048

Published by: webmaster 2010-03-15

Windows server restricts max_open_files to 2048 - enart ::
If you set max_open_files to anything above 2048 (eg 3072) in windows server you'll get something like this in the system events log: Changed limits:
http://enart.investmentpany.com/bkk/bkk-f-lounge-access-439948.htmHOME

If you set max_open_files to anything above 2048 (e.g. 3072) in windows server you'll get something like this in the system events log:

Changed limits: max_open_files: 2048 max_connections: 500 table_cache: 769

It will obey the max_connections: but based on the settings of max_connections: it will replace table_cache: with it's own setting.

Any ideas windows guys?

what version of mysql you using ? maybe reinstalling latest version for your series ie. mysql 4.0.x update to 4.0.27 and 4.1.x update to 4.1.22 or 5.0.x update to 5.0.27 as it seems to have helped this guy http://bugs.mysql.com/bug.php?id=22300

The Old New Thing : No matter where you put an advanced setting ::
The laptop mfrs only put them there in the first place because Windows has .. the header value of MAX_OPEN_FILES you could build the static file table with a of corporate restrictions, not something that brings value to the user. people will be prevented from using it before the server judge that the
http://blogs.msdn.com/oldnewthing/archive/2008/01/14/7103585.aspxHOME

That does not work for Windows 2003 server. The REG paths don't even exist.

Anything for MS 2003 server?

what version of windows and mysql are you using ?

This is most likely a WinNT operating system bug. Bug listed at http://bugs.mysql.com/bug.php?id=24509

MySQL Bugs: #21915: Changing limits of table_cache when setting ::
Your MySQL connection id is 3 to server version: 5.1.12-beta-nt Type . I still get: Changed limits: max_open_files: 2048 max_connections: 500 table_cache: 769 Also would the performance on Windows servers be improved on "busy"
http://bugs.mysql.com/21915HOME

==== Issue explained ====
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=0728
NT Server is limited to 2048 open files per connection. 23-Sep-98

Windows NT multiplexes all file requests to a single server over one virtual circuit. The SMB (Server Message Block) reserves 11 bits for the file handle, resulting in a maximum of 2048 file handles per connection.

This is not normally a problem, but Windows NT Terminal Server's use of the same SMB structure. When a Windows NT Terminal Server connects to a network share, it supplies the servers credentials, which allows multiple Workstations using the Terminal Server to share the virtual circuit, but still have their own security relected. If this network share is for a file-intensive application, the 2048 open file limit may be reached.

If 200 Windows NT Terminal Server users were simultaneously using the share, they would be limited to 10 open files per user. The only real solution is to add more Windows NT Terminal Servers.

=== work around ===
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1180