Create AbusiveUserMapper to replicate an abusive user's workload #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
csgregorian
commented
Apr 1, 2019
| * creation). This uses {@link TimedInputFormat}; see its Javadoc for configuration information. Only requires the | ||
| * NameNode, does not make file data changes. | ||
| * | ||
| * <p>Configuration options available: |
There was a problem hiding this comment.
I feel like the wording is a bit weird on some of these descriptions, suggestions welcome!
...ter-workload/src/main/java/com/linkedin/dynamometer/workloadgenerator/AbusiveUserMapper.java
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new
WorkloadMapper,AbusiveUserMapper, that creates two types of tasks: small operations (single file listing or single folder creation) and large listing operations (configurable # of files). This is useful to see the interaction of users that have dramatically different performance impacts and resource usage. The proportion of small to large/abusive users and the number of mappers for each is configurable.