Taras Ledkov commented on IGNITE-2356:

Looks like the tests {{IgniteHadoopFileSystemShmemEmbedded*}} are not useful 
because when the flag {{skipEmbed}} is set to {{true}} these tests are 
equivalent to the {{IgniteHadoopFileSystemLoopbackEmbedded*}}. It happens 
because in-process Ignite is available always for the tests. So, when it is not 
skipped this type of delegate is used with the highest priority.

I'll add 4 tests for Ignite client -based IGFS delegate (for primary, proxy & 
both dual modes).
There is a problem with client reconnection to the topology after all servers 
are down. Root cause is the inconsistent configuration of the client node & 
server nodes.

> IGFS client should be able to failover in case of server crash.
> ---------------------------------------------------------------
>                 Key: IGNITE-2356
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2356
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: IGFS
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>            Priority: Critical
>             Fix For: 1.8
> IGFS client (IgniteHadoopFileSystem) communicates IGFS over endpoint - either 
> TCP or shmem.
> Only single endpoint can be specified. As such, should the server went down, 
> IgntieHadoopFileSystem (either new or existing) is no longer operational. 
> We need to let user specify several endpoints and failover/balance between 
> them.
> Look at Hadoop HA first to get an ideas on how to configure multiple 
> addresses.

This message was sent by Atlassian JIRA

Reply via email to