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

In multitenant app, drop all nodes for big topologies #3384

Merged
merged 2 commits into from
Nov 1, 2018

Conversation

bboreham
Copy link
Collaborator

As a protection against overloading the app server, drop topologies that have really large node counts. In practice we only see this with runaway numbers of zombie processes.

I've only wired this in to the AWS collector, since that is where we felt the pain.

Also some refactoring of the AWS collector parameters where the duplication started to get annoying.

@bboreham bboreham changed the title Drop all nodes for big topologies In multitenant app, drop all nodes for big topologies Oct 13, 2018
@satyamz
Copy link
Contributor

satyamz commented Oct 16, 2018

@bboreham I am looking into this,
How do I run multi tenant app ? I mean apart from options -app.collector & -app.collector.s3, do I need to setup anything?
I am setting up dynamodb & s3 in my aws account.

@bboreham
Copy link
Collaborator Author

@satyamz thanks for looking.
I think you also need --app.userid.header=X-Scope-OrgID to set how it finds the tenant ID.

@bboreham bboreham merged commit ee0ce7b into master Nov 1, 2018
@bboreham bboreham deleted the drop-big-topologies branch September 13, 2019 15:33
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

3 participants