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/10/03 12:47:00 UTC
[jira] [Commented] (IGNITE-13516) Folder binary_meta/$consistentId
created for in-memory cluster and failed to start the node sometimes
[ https://issues.apache.org/jira/browse/IGNITE-13516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206688#comment-17206688 ]
Ignite TC Bot commented on IGNITE-13516:
----------------------------------------
{panel:title=Branch: [pull/8308/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8308/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Binary Objects{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5638813]]
* {color:#013220}IgniteBinaryObjectsTestSuite: BinaryMetadataInMemoryTest.testBinaryMetadataDir - PASSED{color}
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5638928&buildTypeId=IgniteTests24Java8_RunAll]
> Folder binary_meta/$consistentId created for in-memory cluster and failed to start the node sometimes
> -----------------------------------------------------------------------------------------------------
>
> Key: IGNITE-13516
> URL: https://issues.apache.org/jira/browse/IGNITE-13516
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.9
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Blocker
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For in-memory cluster consistentId is generated in the old style, using all local addresses. This consistent id can sometimes have a length of more than 255 chars and can't be used as a directory name. After IGNITE-11073 Ignite always creates folder binary_meta/$consistentId, but this folder should be created only if persistence is enabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)