Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
Reviewed
Description
We need to be able to understand the capacity model for the timeline server to give users the tools they need to deploy a timeline server with the correct capacity.
I propose we create a mapreduce job that can measure timeline server write and read performance. Transactions per second, I/O for both read and write would be a good start.
This could be done as an example or test job that could be tied into gridmix.
Attachments
Attachments
Issue Links
- is related to
-
YARN-4341 add doc about timeline performance tool usage
- Resolved
- relates to
-
MAPREDUCE-6335 convert load test driver to timeline service v.2
- Resolved
-
MAPREDUCE-6546 reconcile the two versions of the timeline service performance tests
- Resolved
-
YARN-3378 a load test client that can replay a volume of history files
- In Progress