You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/02/11 13:25:00 UTC
[jira] [Commented] (IGNITE-12099) Don't write metadata to disk in
discovery thread
[ https://issues.apache.org/jira/browse/IGNITE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034439#comment-17034439 ]
Ignite TC Bot commented on IGNITE-12099:
----------------------------------------
{panel:title=Branch: [pull/7396/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5036477&buildTypeId=IgniteTests24Java8_RunAll]
> Don't write metadata to disk in discovery thread
> ------------------------------------------------
>
> Key: IGNITE-12099
> URL: https://issues.apache.org/jira/browse/IGNITE-12099
> Project: Ignite
> Issue Type: Improvement
> Components: binary
> Reporter: Denis Mekhanikov
> Assignee: Sergey Chugunov
> Priority: Major
>
> When persistence is enabled, binary metadata is written to disk upon registration. Currently it happens in the discovery thread, which makes processing of related messages very slow.
> A different thread should be used to write metadata to disk. Binary type registration will be considered finished before information about it is written to disks on all nodes.
> The implementation should guarantee consistency in cases of cluster restarts.
> Dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Asynchronous-registration-of-binary-metadata-td43021.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)