non-standard MySQL

CommunityUser — Tue, 16 Jun 2015 20:40:31 GMT

I was asked to put AppDynamics in a non-standard configuration by using a version of MySQL other than the bundled version. I know this is strongly discouraged (per https://docs.appdynamics.com/display/PRO40/Controller+Version), but I was asked to try nonetheless. I was able to get the application started, though I didn’t do any comprehensive tests.

Does anyone know what, if any, are the performance implications of running MySQL 5.1 instead of the bundled version?

FWIW, to do this, I made a few adjustments to the db.cnf configuration fie:

# lock_wait_timeout=600 # DS 2015-06-16

# innodb_io_capacity = 200 # NEED PARAMETERIZE - 100 per disk # DS 2015-06-16

# innodb_read_io_threads = 8 # DS 2015-06-16

# innodb_write_io_threads = 8 # DS 2015-06-16

# innodb_buffer_pool_instances=16 # DS 2015-06-16

# innodb_adaptive_flushing=1 # DS 2015-06-16

# innodb_purge_threads=1 # DS 2015-06-16

# innodb_file_format=Barracuda # DS 2015-06-16

# transaction-isolation=READ-COMMITTED # DS 2015-06-16

socket=$APPDYNAMICS_HOME /AppDynamics/Controller/db/mysql.sock

And I created a few softlinks in the filesystem:

ln -s $APPDYNAMICS_HOME/AppDynamics/Controller/db/bin -> $CUSTOM_MYSQL/bin/

ln -s $APPDYNAMICS_HOME/AppDynamics/Controller/db/share/mysql -> $APPDYNAMICS_HOME /AppDynamics/Controller/db/share/

Everything seems to be working properly while launching with no agents reporting, though I did get this warning:

[Warning] Could not increase number of max_open_files to more than 1024 (request: 2036)

Again, I realize this is very frowned upon, and I'm fairly confident this won't be put into production, but I'm curious if anyone has any idea what the performance implications are.

Re: non-standard MySQL

Arun_Dasetty — Wed, 17 Jun 2015 14:13:45 GMT

Hi Daniel,

As you aware it is not recommended to use different version, we have not come across any customers using diffrent mysql version other than bundled we strongly recommend customers to avoid trying different mysql/glassfish artifacts other than bundled with controller.

Regarding the warn message check if the information in following docs helps, see if the warn message resolves:

https://docs.appdynamics.com/display/PRO40/Limit+File+Descriptors+on+Linux

We see as stated in docs 4.x bundles with mysql 5.5.x and using lower mysql version might result in hitting 5.1 version specific bugs or performance issues specific to mysql version, Hope that clarifies.

topic Re: non-standard MySQL in AppD Archive

non-standard MySQL

Re: non-standard MySQL