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.

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

Byi more replicas #23

Merged
merged 3 commits into from May 7, 2019
Merged

Byi more replicas #23

merged 3 commits into from May 7, 2019

Conversation

bin3377
Copy link

@bin3377 bin3377 commented May 6, 2019

Tuning fluentd resource to fix Context canceled issue

  • Use 3 replica rather than 1
  • Reduce Memory from 2Gi to 256Mi (each container)
  • Reduce CPU from 200m to 100m (each container)

Monitoring for couple of hours and looks like no more context canceled error in Prometheus log now

FYI - definition of Kubernetes resource limitation
@frankreno @ggarg2906sumo

@bin3377 bin3377 requested review from samjsong and lei-sumo May 6, 2019 23:12
@@ -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

@bin3377 bin3377 merged commit 6d87b98 into master May 7, 2019
@bin3377 bin3377 deleted the byi-more-replicas branch May 7, 2019 18:38
psaia pushed a commit to psaia/sumologic-kubernetes-collection that referenced this pull request May 25, 2021
* start creating test account resources

* add sumo env var

* move account config into tf config

* tf fmt

* sign pipeline

* specify dag

* limit concurrency

* update

* separate pipelines

* chain the pipelines, remove second fmt step

* move sumo_env to the drone file

* remove vars file

* update pipeline

* remove experiments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants