[ https://issues.apache.org/jira/browse/IGNITE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761193#comment-15761193 ]
Taras Ledkov edited comment on IGNITE-2356 at 12/19/16 1:42 PM: ---------------------------------------------------------------- *1, 2* - done; *3* - Should we support the case when delegate shared ignite instance between pure in-proc connection and Ignite client connection? Looks like it doesn't make sense because the case is happen when the grid name of {{endpoint}} equals to client name. It is a very strange configuration. Correct? was (Author: tledkov-gridgain): *1, 2* - done; 3 - Should we support the case when delegate shared ignite instance between pure in-proc connection and Ignite client connection? Looks like it doesn't make sense because the case is happen when the grid name of {{endpoint}} equals to client name. It is a very strange configuration. Correct? > 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: 2.0 > > > 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 (v6.3.4#6332)