Skip to content
This repository was archived by the owner on Jun 26, 2023. It is now read-only.

S3: Update maxconn and npthread values from haproxy config#1756

Open
sachitanands wants to merge 4 commits into
mainfrom
br/sachit/haproxy-changes
Open

S3: Update maxconn and npthread values from haproxy config#1756
sachitanands wants to merge 4 commits into
mainfrom
br/sachit/haproxy-changes

Conversation

@sachitanands

@sachitanands sachitanands commented Jan 20, 2022

Copy link
Copy Markdown
Contributor

S3: Update maxconn and npthread values from haproxy config if setup size defined in solution.yaml as "large"

we are pointing to maxconn -> 1000 and nbthread -> 16 only in case of setup_size=large.

Signed-off-by: Sachitanand Shelake sachitanand.shelake@seagate.com

Problem Statement

  • Problem statement

Design

  • For Bug, Describe the fix here.
  • For Feature, Post the link for design

Coding

Checklist for Author

  • Coding conventions are followed and code is consistent

Testing

Checklist for Author

  • Unit and System Tests are added
  • Test Cases cover Happy Path, Non-Happy Path and Scalability
  • Testing was performed with RPM

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

  • Interface change (if any) are documented
  • Side effects on other features (deployment/upgrade)
  • Dependencies on other component(s)

Review Checklist

Checklist for Author

  • JIRA number/GitHub Issue added to PR
  • PR is self reviewed
  • Jira and state/status is updated and JIRA is updated with PR link
  • Check if the description is clear and explained

Documentation

Checklist for Author

  • Changes done to WIKI / Confluence page / Quick Start Guide

@sachitanands

Copy link
Copy Markdown
Contributor Author

…up size as Large

Signed-off-by: Sachitanand Shelake <sachitanand.shelake@seagate.com>
@sachitanands
sachitanands force-pushed the br/sachit/haproxy-changes branch from c4dd4fd to 176d82e Compare January 20, 2022 08:48
@vimalraghwani20

Copy link
Copy Markdown
Contributor

@sachitanands 1N deployment job failed. please check

@t7ko-seagate t7ko-seagate left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ok with the change as soon as tests pass.

Signed-off-by: Sachitanand Shelake <sachitanand.shelake@seagate.com>
@stale

stale Bot commented Jan 31, 2022

Copy link
Copy Markdown

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nileshgovande @bkirunge7 @knrajnambiar76 @t7ko-seagate for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

@stale stale Bot removed the needs-attention label Feb 1, 2022
@sachitanands

Copy link
Copy Markdown
Contributor Author

Started 1 node k8 deployment
http://eos-jenkins.mero.colo.seagate.com/job/Cortx-kubernetes/job/deploy-cortx-k8-cluster/985/
we will debug failure today

Signed-off-by: Sachitanand Shelake <sachitanand.shelake@seagate.com>
@stale

stale Bot commented Feb 5, 2022

Copy link
Copy Markdown

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nileshgovande @bkirunge7 @knrajnambiar76 @t7ko-seagate for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

@stale stale Bot added the needs-attention label Feb 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants