0 views collected around this technical thread.
This article explains how MySQL 8.0.32 processes the flush, sync, and commit subphases during a two‑phase commit, detailing the roles of leader and follower threads, log handling, system variables, and the conditions that trigger binlog rotation and persistence.
This article explains MySQL 8.0.32 InnoDB's two‑phase commit process, detailing the flush, sync, and commit sub‑stages, the concept of group commit, and how queues and mutexes coordinate transaction logging to reduce redundant disk writes.
The article explains how executing FLUSH commands on MySQL replicas that are in read_only mode can still write to the binary log, generate new GTIDs, and lead to GTID mismatches between primary and replica, especially when tools like ClickHouse issue such statements.
The PHP function fastcgi_finish_request flushes all pending response data to the client and terminates the request, allowing the server to continue executing time‑consuming tasks after the client connection has closed, and returns TRUE on success or FALSE on failure.
This article explains the full syntax of Python's print() function, describes each parameter (value, sep, end, file, flush), and provides step‑by‑step examples showing how to output single or multiple values, control separators, line endings, redirect output to files, and force flushing.
This article explains the core mechanisms of HBase—Flush and Compaction—detailing why they are needed, the conditions that trigger Flush, the types and triggers of Compaction, and provides practical recommendations for tuning the most important configuration parameters to improve write and read performance.