[
https://issues.apache.org/jira/browse/IGNITE-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452340#comment-17452340
]
Ignite TC Bot commented on IGNITE-16014:
----------------------------------------
{panel:title=Branch: [pull/9615/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9615/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Snapshots{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=6303315]]
* {color:#013220}IgniteSnapshotTestSuite:
IgniteSnapshotManagerSelfTest.testSnapshotThreadPoolSizeUsage[Encryption=true]
- PASSED{color}
* {color:#013220}IgniteSnapshotTestSuite:
IgniteSnapshotManagerSelfTest.testSnapshotThreadPoolSizeUsage[Encryption=false]
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6298166&buildTypeId=IgniteTests24Java8_RunAll]
> Add configuration for snapshot thread pool size
> -----------------------------------------------
>
> Key: IGNITE-16014
> URL: https://issues.apache.org/jira/browse/IGNITE-16014
> Project: Ignite
> Issue Type: Task
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Critical
> Labels: iep-43
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the snapshot thread pool size is hardcoded with a value of 4. This
> may lead to high disk utilization resources on slow SAS hard drives. The user
> must be able to configure the snapshot thread pool size must be and this
> thread pool also must be available for monitoring.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
