How to change default-storage-engine in MySQL

When creating a table, the ENGINE option is used, which specifies the storage engine, if this option is not specified in the SQL query, then the default storage engine is used, which is specified in the MySQL server configuration file or when it starts mysqld –default-storage-engine=InnoDB.

Continue reading “How to change default-storage-engine in MySQL”

Configuring Multicast on Eltex MES2324B

Once I needed to receive Multicast traffic from different TV providers and from different VLANs, so I had to use access-list in order to correctly transmit the igmp-report from the client to the required VLAN. If Multicast is in only one VLAN, then you can do without access-list.

Continue reading “Configuring Multicast on Eltex MES2324B”

Solution for warning Asked to transmit frame type ulaw, while native formats is (g729) read/write = ulaw/ulaw

Once a user made a call and Asterisk began to display a lot of warnings, and there was also no sound:

Continue reading “Solution for warning Asked to transmit frame type ulaw, while native formats is (g729) read/write = ulaw/ulaw”

Changing innodb_flush_log_at_trx_commit in MySQL

Default value is 1, possible values are 0-2.

0 – Logs are written and flushed to disk once per second. Transactions that have not been flushed out can be lost as a result of a crash.
1 – Logs are written and flushed to disk every time a transaction is committed.
2 – Logs are written after each commit of a transaction and flushed to disk once per second. Transactions that have not been flushed out can be lost in the event of a failure.

Continue reading “Changing innodb_flush_log_at_trx_commit in MySQL”

How to change innodb_thread_concurrency in MySQL

I will give an example of changing innodb_thread_concurrency in MySQL.
Since InnoDB uses operating system threads to process user transactions, the innodb_thread_concurrency parameter allows you to limit them. By default in new MySQL versions the value is 0, which means that there is no limit on the number of simultaneously executed threads and this is correct for modern servers. If you want to limit, then when the limit is reached, the extra threads will wait a certain number of microseconds specified in the innodb_thread_sleep_delay parameter, and then try to get into the queue. Also in MySQL 5.6.3 and higher, the innodb_adaptive_max_sleep_delay parameter was added which allows you to specify the maximum number of microseconds for the innodb_thread_sleep_delay parameter and then InnoDB automatically adjusts innodb_thread_sleep_delay.

Continue reading “How to change innodb_thread_concurrency in MySQL”