-
Story
-
Resolution: Done
-
Highest
-
None
-
None
-
LOG Sprint 10, LOG Sprint 11
Will fix the temporary workaround for performance in LOG-376
starting 20180518
on cd.onap.info
ubuntu@ip-172-31-56-71:~$ sudo vi oom/kubernetes/log/charts/log-logstash/templates/deployment.yaml
-kind: Deployment
+kind: DaemonSet
- replicas: {{ .Values.replicaCount }}
values.yaml
- replicaCount: 3
- blocks
-
LOG-376 Logstash full saturation of 8 cores with AAI deployed on one of the quad 8 vCore vms for 30 logs/sec - up replicaSet 1 to 3 or use DaemonSet
-
- Closed
-
-
LOG-587
Refactor Filebeat per uService sidecar as per VM DaemonSet
-
- Closed
-
-
LOG-841
Logstash container - use a label to distribute the ReplicaSet instead of DaemonSet
-
- Closed
-
- is duplicated by
-
LOG-165
Platform Maturity: replica scaling for elasticsearch and logstash containers
-
- Closed
-
- relates to
-
LOG-258
S3P ELK stack performance and clustering
-
- Closed
-
-
LOG-380
Platform Maturity: Performance, Stability, Resiliency, Scalability
-
- Closed
-
- links to
