Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Byi more replicas #23

Merged
merged 3 commits into from
May 7, 2019
Merged

Byi more replicas #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
69dca24
make fluentd deploy with 3 replica
May 6, 2019
6d57648
less mem/cpu resource taken
May 6, 2019
adff6ab
add missing cfs_throttled
May 6, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy/helm/overrides.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ prometheus:
regex: POD
sourceLabels: [container_name]
- action: keep
regex: kubelet;container_cpu_(?:load_average_10s|(?:system|usage)_seconds_total)
regex: kubelet;container_cpu_(?:load_average_10s|(?:system|usage|cfs_throttled)_seconds_total)
sourceLabels: [job, __name__]
- url: http://fluentd:9888/prometheus.metrics.container
writeRelabelConfigs:
Expand Down
10 changes: 5 additions & 5 deletions deploy/kubernetes/fluentd-sumologic.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ spec:
selector:
matchLabels:
k8s-app: fluentd-sumologic
replicas: 1
replicas: 3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any data duplication with 3 replicas of Fluentd running? Or when Prometheus writes to the remote write endpoint do the metrics only get sent to one of the 3 replicas?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No data duplication. the idea is much similar as our receiver nodes. from outside (e.g. Prometheus) there is only single endpoint (which we defined as a kubernetes service). The traffic will be distributed to 3 nodes. We don't have any session or partition concept here so basically it's just randomly pick anyone

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks for confirming

template:
metadata:
labels:
Expand All @@ -176,11 +176,11 @@ spec:
imagePullPolicy: Always
resources:
limits:
memory: 2Gi
cpu: "200m"
memory: 256Mi
cpu: "100m"
requests:
memory: 2Gi
cpu: "200m"
memory: 256Mi
cpu: "100m"
ports:
- name: prom-write
containerPort: 9888
Expand Down