core scheduler, app fabric and dataset service should use fewer threads in tests
Description
Release Notes
None
Activity
Show:
Andreas Neumann September 14, 2018 at 11:53 PM
PR for app fabric and dataset service: https://github.com/caskdata/cdap/pull/10609
Ran the DUT for two weeks on regular basis, did not observe flakiness that was not observed in develop.
Andreas Neumann August 27, 2018 at 7:01 PM
they might. But they are unit tests and not integration tests. A unit test should not have to spin up a full-fledged system. It also makes debugging and reading logs harder if there are hundreds of thread trace-logging.
Andreas Neumann August 27, 2018 at 6:59 PM
PR for core scheduler: https://github.com/caskdata/cdap/pull/10584
Ali Anwar August 27, 2018 at 6:10 PM
Don't the unit tests run with enough resources to support these number of threads?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created August 25, 2018 at 1:23 AM
Updated September 14, 2018 at 11:53 PM
Resolved September 14, 2018 at 11:53 PM
Dataset service has 10 workers and 30 executors
AppFabric has 10 workers and 20 executors
Scheduler has 15 constraint checker threads