[IGNITE-4103] IgniteDataStreamer doesn't throw exception if cache is destroyed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.7
• Fix Version/s: 1.8
• Component/s: cache
• Assignee: Saikat Maitra
• Reporter: Valentin Kulichenko
• Created: 21/Oct/16 19:25
• Updated: 17/Nov/16 16:52
• Resolved: 17/Nov/16 16:51

Description

Test reproducing the issue is attached.

When a streamer streams the data and someone concurrently destroys the cache, addData doesn't throw an exception. Code continues to work and a lot of messages like this appear in the log:

[12:20:38,451][ERROR][main][CacheObjectBinaryProcessorImpl] Failed to get partition

The problematic code is in IgniteCacheObjectProcessorImpl.partition(...) method:

try {
    return cctx != null ?
        cctx.affinity().partition(obj, false) :
        ctx.kernalContext().affinity().partition0(ctx.cacheName(), obj, null);
}
catch (IgniteCheckedException e) {
    U.error(log, "Failed to get partition");

    return  -1;
}

There are two issues here:

1. Exception is completely ignored, it's not even printed out in U.error.
2. The exception should be actually rethrown so that streamer can stop adding data.

Issue Links

• is duplicated by: IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails
• is part of: IGNITE-500 CacheLoadingConcurrentGridStartSelfTest fails
• links to: GitHub Pull Request #1186