ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-4205) CassandraCacheStore should start IgniteThread threads in loadCache() method
Date Thu, 10 Nov 2016 00:56:58 GMT
Valentin Kulichenko created IGNITE-4205:

             Summary: CassandraCacheStore should start IgniteThread threads in loadCache()
                 Key: IGNITE-4205
                 URL: https://issues.apache.org/jira/browse/IGNITE-4205
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 1.7
            Reporter: Valentin Kulichenko

{{CassandraCacheStore.loadCache()}} method starts a generic thread pool for parallel data
load. Threads in this thread pool can't deserialize Ignite internal objects (e.g. {{IgniteKernal}})
which can cause unexpected behavior. Here is one of the scenarios:
* There is column in Cassandra which stores an object as BLOB using {{JavaSerializer}}.
* {{CacheConfiguration.storeKeepBinary}} is {{true}}.
* When an object is saved, it's passed to the store as an instance of {{BinaryObject}} which
is converted to a byte array and saved in Cassandra.
* When the same object is loaded in {{loadCache}}, the store takes the byte array and tries
to convert it to {{BinaryObject}}. But it can't because this implies calling {{IgnitionEx.localIgnite()}}
from non-Ignite thread.

To fix this we need to provide a thread factory that will create instances of {{IgniteThread}}
and use it in the pool that loads the data.

Most likely the same issue exists in {{CacheAbstractJdbcStore}}.

And in general, any threads created by Ignite internals should be {{IgniteThread}}-s. This
should be revisited.

This message was sent by Atlassian JIRA

View raw message