[IGNITE-6788] Ignite WAL reader fails on Tx marker record for persistent store with new style folder naming

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.4
• Component/s: persistence
• Assignee: Dmitry Pavlov
• Reporter: Dmitry Pavlov
• Created: 30/Oct/17 11:45
• Updated: 01/Nov/17 14:43
• Resolved: 01/Nov/17 00:42

Description

After chaning paths generation and consistent ID to be UUID
also after introduction of Tx Markers
WAL records iterator begin to fail to deserialize consistentID from TX record in mode when binary_meta and marshaller cache paths are not provided

Caused by: java.lang.NullPointerException
	at org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
	at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
	at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.readConsistentId(TxRecordSerializer.java:211)
	at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.TxRecordSerializer.readTxRecord(TxRecordSerializer.java:114)
	at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.readRecord(RecordDataV1Serializer.java:812)
	at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer$1.readWithHeaders(RecordV1Serializer.java:96)
	at org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:230)
	... 18 more

Issue Links

• relates to: IGNITE-5558 Add ability to read WAL outside of an Ignite node
• links to: GitHub Pull Request #2945