[
https://issues.apache.org/jira/browse/IGNITE-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660240#comment-16660240
]
Ignite TC Bot commented on IGNITE-9418:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 TIMEOUT
, Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2145023]]
* IgniteSqlSplitterSelfTest.testIndexSegmentationPartitionedReplicated (last
started)
{color:#d04437}MVCC JDBC{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2141514]]
*
JdbcThinTransactionsServerAutoCommitComplexSelfTest.testRepeatableReadWithConcurrentCacheReplace
(last started)
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2141566&buildTypeId=IgniteTests24Java8_RunAll]
> Avoid initialize file page store manager for caches during PME synchronously
> ----------------------------------------------------------------------------
>
> Key: IGNITE-9418
> URL: https://issues.apache.org/jira/browse/IGNITE-9418
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.5
> Reporter: Pavel Kovalenko
> Assignee: Stanilovsky Evgeny
> Priority: Critical
> Fix For: 2.8
>
>
> Currently, we do creation for partition and index files during PME for
> starting caches at the beginning of
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#readCheckpointAndRestoreMemory
> method.
> We should avoid this because sometimes it took a long time as we perform
> writing to disk.
> If the cache was registered during PME we should initialize page store lazy
> or asynchronously.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
