broadcastmanager.go:117: Not providing client [IP] with cert because client's buffer is full. The client can't keep up. Skipped certs: 135001 #70
-
|
Sometimes, but not regularly, I keep receiving the message:
I understand this is a client issue, but is there any server parameter in the config.yaml file I can adjust to eliminate or reduce the issue? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
This log is written when the client is not able to process the certificates as fast as the server is downloading them. The only way to properly handle this is by improving your client's processing speed. certstream-server-go does not store certificates, so it operates at exactly the speed at which the certificates are published to the different CT logs. If a client is not fast enough, there is nothing we can do on the server side except skipping certificates. Buffering every certificate would quickly lead to a massive storage problem. |
Beta Was this translation helpful? Give feedback.
-
|
Throwing a queue in between (say kafka) should solve the slow client problem, as the client can consume certs from the queue at any pace it desires, take a look at #72 (Stream Processing Support (W.I.P)) |
Beta Was this translation helpful? Give feedback.
This log is written when the client is not able to process the certificates as fast as the server is downloading them. The only way to properly handle this is by improving your client's processing speed. certstream-server-go does not store certificates, so it operates at exactly the speed at which the certificates are published to the different CT logs.
If a client is not fast enough, there is nothing we can do on the server side except skipping certificates. Buffering every certificate would quickly lead to a massive storage problem.