Re: 95f2a07d323: MDEV-33582 Add more warnings to be able to better diagnose network issues

Hi, Michael, On Mar 04, Michael Widenius wrote:
"to the error log"
- In case of a of not being able to read or write a packet, a more detailed
"of a of" ?
"seems" I don't understand why it happens and whether it's normal or not, and if normal, why it's normal only for semisync and not normal otherwise.
why are these errors "normal" and can be ignored?
error 11? "Resource temporarily unavailable"? What does it mean in this context?
do you mean, it's for performance reasons?
+
Regards, Sergei Chief Architect, MariaDB Server and security@mariadb.org

Hi! On Tue, Mar 5, 2024 at 1:47 AM Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Michael,
<cut>
I changed the code to assume that when recv() returns 0 and errno = 0 this is actually a communication error. This fixed the issues and I could remove the flag. <cut>
These are only printed as part of 'extended logging' when using --log-warnings=4 and used to produce extra information (not errors) why things happens. Many of the errors are also depending on timing so it is better to suppress them. We also do not have any other option than suppress these, as they are not part of any result set. <cut>
mtr --mysqld=--log-warnings=4 rpl_extra_col_master_innodb Produces 3 lines on the master and 12 times on the slave of type: var/log/mysqld.2.err:2024-03-05 20:10:34 6 [ERROR] mariadbd: Could not read packet: fd: 68 state: 2 remain: 4 errno: 11 vio_errno: 1158 length: 0 This comes from killing connections and disconnecting slaves in the test Probably that the connection as
Yes, that was the original intent. However, I have now removed this as I was able to find and fix the source of the problem. Thanks for the review! Regards, Monty
participants (2)
-
Michael Widenius
-
Sergei Golubchik