You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This change exposes the ingress buffer configuration parameters to the
outside world.
Sometimes, depending on the scaling of Log Cache, the number of sources (CF applications and platform components) and the log load, ingress drops may occur when Log Cache nodes send items between each other. The Log Cache `ingress_dropped` metric should be monitored, to make sure that there are no drops. For such cases, the following three parameters can be adjusted until the log loss is gone.
- Ingress Buffer Size - The ingress buffer (diode) size in number of items used when LogCache nodes send items between each other. The default size is 10000. Can be increased when ingress drops occur.
- Ingress Buffer Read Batch Size - The ingress buffer read batch size in number of items. The size of the ingress buffer read batch used when LogCache nodes send items between each other. The default size is 100. Can be increased when ingress drops occur.
- Ingress Buffer Read Batch Interval - The ingress buffer read interval in milliseconds. The default value is 250. Can be increased when ingress drops occur.
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,13 @@ Memory limit - Increasing memory limit allows for more storage, but may cause ou
43
43
44
44
Larger CPUs - Increasing the CPU budget per instance should allow higher throughput
45
45
46
+
Sometimes, depending on the scaling of Log Cache, the number of sources (CF applications and platform components) and the log load, ingress drops may occur when Log Cache nodes send items between each other. The Log Cache `ingress_dropped` metric should be monitored, to make sure that there are no drops. For such cases, the following three parameters can be adjusted until the log loss is gone.
47
+
48
+
- Ingress Buffer Size - The ingress buffer (diode) size in number of items used when LogCache nodes send items between each other. The default size is 10000. Can be increased when ingress drops occur.
49
+
- Ingress Buffer Read Batch Size - The ingress buffer read batch size in number of items. The size of the ingress buffer read batch used when LogCache nodes send items between each other. The default size is 100. Can be increased when ingress drops occur.
50
+
- Ingress Buffer Read Batch Interval - The ingress buffer read interval in milliseconds. The default value is 250. Can be increased when ingress drops occur.
51
+
52
+
46
53
Log Cache is known to exceed memory limits under high throughput/stress. If you see your log-cache reaching higher memory
47
54
then you have set, you might want to scale your log-cache up. Either solely in terms of CPU per instance, or more instances.
Copy file name to clipboardExpand all lines: jobs/log-cache/spec
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,18 @@ properties:
47
47
description: "The maximum number of items stored in LogCache per source."
48
48
default: 100000
49
49
50
+
ingress_buffer_size:
51
+
description: "The ingress buffer (diode) size in number of items. The size of the ingress buffer used when LogCache nodes send items between each other. In some cases, the buffer size must be risen in order to avoid ingress drops. Must be an integer."
52
+
default: 10000
53
+
54
+
ingress_buffer_read_batch_size:
55
+
description: "The ingress buffer read batch size in number of items. The size of the ingress buffer read batch used when LogCache nodes send envelopes between each other. In some cases, the batch size must be risen in order to make place in the buffer faster and avoid ingress drops. Must be an integer."
56
+
default: 100
57
+
58
+
ingress_buffer_read_batch_interval:
59
+
description: "The ingress buffer read batch interval in milliseconds. The interval in which the data will be read out from the ingress buffer used when LogCache nodes send envelopes between each other. In some cases, the batch read interval must be adjusted in order to make place in the buffer faster and avoid ingress drops. Must be an integer."
60
+
default: 250
61
+
50
62
truncation_interval:
51
63
description: "The amount of time between log-cache checking if it needs to prune"
0 commit comments