Hello!

Please refer to
https://ignite.apache.org/docs/latest/key-value-api/binary-objects#recommendations-on-binary-objects-tuning

It seems that some of the rows in the table has a layout of data which is
not present on any of nodes. So Ignite does not know how to unpack these
rows into columns.

Maybe you have lost the contents of binary_meta directory on the nodes or
something like that.

Regards,
-- 
Ilya Kasnacheev


пн, 24 мая 2021 г. в 15:50, Naveen <[email protected]>:

> HI
>
> We are using Ignite 2.8.1
>
> when we run select * table, it throws below exception, how ever querying
> for
> a specific key works fine.
> what could have gone wrong here ? Anything we can make out with these ids
> mentioned below
> Error: Failed to execute map query on remote node
> [nodeId=3db2b3e5-21ae-46ad-9b14-cf3a1c8171de, errMsg=Failed to execute SQL
> query. General error: "class
> org.apache.ignite.binary.BinaryObjectException:
> Cannot find schema for object with compact footer
> [typeName=org.ignite.model.curated.Account, typeId=-2143671743,
> missingSchemaId=319535867, existingSchemaIds=[-284217025, -131460726,
> 738773736, -361085461, 130249633, -1686791135, 670818893, 1018521906,
> -978489660, 1225415027, 1484800635, 469100171]]"; SQL statement:
>
> [2021-05-24 16:42:58,117][WARN
> ][client-connector-#78][CacheObjectBinaryProcessorImpl] Schema is missing
> while no metadata updates are in progress (will wait for schema update
> within timeout defined by IGNITE_WAIT_SCHEMA_UPDATE system property)
> [typeId=-2143671743, missingSchemaId=319535867, pendingVer=3,
> acceptedVer=3,
> binMetaUpdateTimeout=30000]
>
> Thanks
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to