This message appear multiple times in a sync from hubspot to big query, what it is meaning? 2025-02-10 143551 destination INFO pool-3-thread-1 i.a.c.i.d.a.b.BufferManager(printQueueInfo):94 [ASYNC QUEUE INFO] Global: max: 742.41 MB, allocated: 10 MB (10.0 MB), %% used: 0.013469714189502041 | State Manager memory usage: Allocated: 10 MB, Used: 0 bytes, percentage Used 0.0 130 2025-02-10 143551 destination INFO pool-6-thread-1 i.a.c.i.d.a.FlushWorkers(printWorkerInfo):127 [ASYNC WORKER INFO] Pool queue size: 0, Active threads: 0

This log message is related to Airbyte's destination connector for BigQuery, specifically concerning its memory usage and worker status during a sync from HubSpot to BigQuery. Let me break down the meaning of this message for you: 1. Memory Usage: The first line provides information about the buffer manager's memory allocation: - Maximum available memory: 742.41 MB - Currently allocated: 10 MB - Percentage used: 0.013469714189502041% (very low usage) This indicates that the destination connector has a large amount of memory available (742.41 MB) but is currently using very little of it (only 10 MB). 2. State Manager: - Allocated: 10 MB - Used: 0 bytes - Percentage Used: 0.0% This shows that the State Manager, which keeps track of the sync state, has allocated 10 MB but is not actively using any of it at the moment. 3. Worker Information: The second line provides information about the worker threads: - Pool queue size: 0 (no pending tasks) - Active threads: 0 (no threads currently working) This message appears multiple times because it's a periodic status update that Airbyte logs to provide visibility into the destination connector's resource usage during the sync process. The low memory usage and absence of active workers suggest that at these particular moments, the destination connector was not actively processing data. This behavior is normal and doesn't necessarily indicate a problem. It could mean that the connector is waiting for data from the source (HubSpot in this case) or that it has finished processing a batch and is waiting for the next one. For more detailed information about Airbyte's logging and performance monitoring, you can refer to the [Airbyte Documentation](https://docs.airbyte.com/).