Mikael,

Please, let us know if the issue occurs again and no work directories were
deleted and no files can be shared between nodes.
We'll investigate this. Any reproducer will be appreciated.

On Tue, Mar 27, 2018 at 1:40 PM, Andrey Mashenkov <
[email protected]> wrote:

> Hi Mikael,
>
> Please check if ignite work directories were not  cleaned in between.
> Also check if every node have separate work directory and no files can be
> shared.
>
> Otherwise, it looks like a race.
> As a workaround you can specify Classes that can be serialized (Service
> classes, Key\Value classes)
> in BinaryConfiguration.setClassNames() to force Ignite register classes
> at startup.
>
>
>
> On Tue, Mar 27, 2018 at 1:25 PM, Mikael <[email protected]> wrote:
>
>> Hi!
>>
>> I stopped my application without problems last week, today when I started
>> it up (no changes to the code or anything) I got the exception below,
>> anyone have a clue to what it could be ?
>>
>> It's 2.4, I have native persistence on.
>>
>> 12:13:13 [srvc-deploy-#56] ERROR: Failed to initialize service (service
>> will not be deployed): RTU_1_10
>> org.apache.ignite.IgniteCheckedException: Cannot find metadata for
>> object with compact footer: -389806882
>>     at 
>> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9908)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor.copyAndInject(GridServiceProcessor.java:1422)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor.redeploy(GridServiceProcessor.java:1343)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor.processAssignment(GridServiceProcessor.java:1932)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor.onSystemCacheUpdated(GridServiceProcessor.java:1595)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor.access$300(GridServiceProcessor.java:124)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1577)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.processors.service.GridServicePro
>> cessor$DepRunnable.run(GridServiceProcessor.java:2008)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> [?:1.8.0_144]
>>     at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> [?:1.8.0_144]
>>     at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
>> Caused by: org.apache.ignite.binary.BinaryObjectException: Cannot find
>> metadata for object with compact footer: -389806882
>>     at org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCr
>> eateSchema(BinaryReaderExImpl.java:2008) ~[ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> org.apache.ignite.internal.binary.BinaryReaderExImpl.<init>(BinaryReaderExImpl.java:284)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> org.apache.ignite.internal.binary.BinaryReaderExImpl.<init>(BinaryReaderExImpl.java:183)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> org.apache.ignite.internal.binary.BinaryReaderExImpl.<init>(BinaryReaderExImpl.java:162)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.internal.binary.GridBinaryMarshaller.deser
>> ialize(GridBinaryMarshaller.java:310) ~[ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller
>> .unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>> ~[ignite-core-2.4.0.jar:2.4.0]
>>     at 
>> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9902)
>> [ignite-core-2.4.0.jar:2.4.0]
>>     ... 10 more
>>
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>



-- 
Best regards,
Andrey V. Mashenkov

Reply via email to