Flume報 Space for commit to queue couldn't be acquired. Sinks are likely not keeping up with sources, or the buffer size is too tight - 碼上快樂

相關內容簡體繁體

Flume報 Space for commit to queue couldn't be acquired. Sinks are likely not keeping up with sources, or the buffer size is too tight

本文轉載自查看原文 2018-03-30 11:50 1121

報這個錯誤需要一個是flume堆內存不夠.還有一個就是把channel的容器調大

在channel加配置

type	-	組件類型名稱必須是`memory`
capacity	100	存儲在 Channel 當中的最大 events 數
transactionCapacity	100	同時刻從Source 獲取，或發送到 Sink 的最大 events 數
keep-alive	3	添加或刪除一個 event 超時的秒數

如果每分鍾開頭量比較大,keep-alive需要調大

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. vagrant up提示"Couldn't open file /path/to/base"的錯誤解決方法 \bin\sh.exe:*** Couldn't reserve space for cygwin's heap,Win32 error 0 Tomcat8啟動報there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache 關於socket buffer size的調優 mysql 參數：[read_buffer_size] [sort_buffer_size] [read_rnd_buffer_size] [tmp_table_size]---圖解 java.net.SocketException: No buffer space available 淺談innodb_buffer_pool_size的設置 bulk_insert_buffer_size and InnoDB 關於：size_t和size_type（轉抄）

粵ICP備18138465號 © 2018-2025 CODEPRJ.COM