Closed mohit84 closed 3 years ago
/run regression
/run full regression
/run brick-mux regression
/run regression
/run regression
/run regression
/run smoke
/run regression
/run full regression
/run regression
/run regression
/run regression
/run smoke
/run regression
/run regression
/run regression
/run brick-mux regression
/run regression
/run brick-mux regression
/run regression
/run brick-mux regression
/run regression
/run regression
/run full regression
/run full regression
/run regression
/run regression
/run brick-mux regression
/run regression
/run brick-mux regression
/run brick-mux regression
/run brick-mux regression
/run brick-mux regression
/run brick-mux regression
/run brick-mux regression
/run regression
/run brick-mux regression
Reviewing amended patches is very time consuming. Could you resent the latest changes as a new commit in the PR ?
/run regression
/run regression
/run brick-mux regression
/run regression
/run full-regression
/run full regression
/run regression
/run full regression
/run brick-mux regression
/run full regression
/run brick-mux regression
/run brick-mux regression
Currently posix xlator spawns posix_disk_space_threads per brick and in case of brick_mux environment while glusterd attached bricks at maximum level(250) with a single brick process in that case 250 threads are spawned for all bricks and brick process memory size also increased.
Solution: Attach a posix_disk_space thread with glusterfs_ctx to spawn a thread per process basis instead of spawning a per brick
Fixes: #1482 Change-Id: I8dd88f252a950495b71742e2a7588bd5bb019ec7 Signed-off-by: Mohit Agrawal moagrawa@redhat.com