Shared memory communication and recovery

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Shared memory communication and recovery

Valentin Kulichenko
Folks,

It's a know fact that shared memory communication doesn't work well and can
cause various issues under load and in case of node failures. In my
understanding the main reason for that the recovery mechanism are not
properly applied in this case, but there can be other issues as well.

However, we still have this option, and moreover it's enabled by default.

In my opinion we should do something with this in 2.0. We can either
completely remove shared memory from communication SPI, or disable it by
default, or fix it. Does anyone knows what kind of effort is needed to do
the latter? Semyon or Yakov, can you comment on this?

-Val
Reply | Threaded
Open this post in threaded view
|

Re: Shared memory communication and recovery

dsetrakyan
To my knowledge, the shared memory communication was added to enable large
file transfers from HDFS to Ignite. Does that use case still make sense or
is the socket communication as fast as shared memory one now?

On Mon, Aug 15, 2016 at 2:38 PM, Valentin Kulichenko <
[hidden email]> wrote:

> Folks,
>
> It's a know fact that shared memory communication doesn't work well and can
> cause various issues under load and in case of node failures. In my
> understanding the main reason for that the recovery mechanism are not
> properly applied in this case, but there can be other issues as well.
>
> However, we still have this option, and moreover it's enabled by default.
>
> In my opinion we should do something with this in 2.0. We can either
> completely remove shared memory from communication SPI, or disable it by
> default, or fix it. Does anyone knows what kind of effort is needed to do
> the latter? Semyon or Yakov, can you comment on this?
>
> -Val
>