Best effort affinity: NPE on topology version check

[Dmitry Melnichuk]

Igniters,

I am currently trying to teach my thin client (pyignite) a new trick
called “Best effort affinity”.

I have been told that this feature is being implemented in the private
branch [1], so I checked it out, built it, and gave it a go.

The handshake goes as expected, I have actually managed to read the
node UUID. But on any subsequent request the server disconnects and
shows the following on its console:

[ERROR][client-connector-#60][ClientListenerNioListener] Failed to
process client request [
req=o.a.i.i.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest@43e45ce3
]
java.lang.NullPointerException

The full dump is in attachment.

Since I am not authorized to create an issue in the repository I was
using, I have to address my question to this list. If anybody involved
in server-side implementation of best effort affinity is reading this,
please tell me am I doing something wrong, or it is an actual bug? How
can this issue be resolved?

[1] https://github.com/gridgain/apache-ignite/tree/ignite-iep23

[Igor Sapego-2]

This is my branch. I fixed an issue so re-merge and check if it helps.

Best Regards,
Igor


On Tue, Feb 19, 2019 at 8:14 AM Dmitry Melnichuk <
[hidden email]> wrote:

> Igniters,
>
> I am currently trying to teach my thin client (pyignite) a new trick
> called “Best effort affinity”.
>
> I have been told that this feature is being implemented in the private
> branch [1], so I checked it out, built it, and gave it a go.
>
> The handshake goes as expected, I have actually managed to read the
> node UUID. But on any subsequent request the server disconnects and
> shows the following on its console:
>
> [ERROR][client-connector-#60][ClientListenerNioListener] Failed to
> process client request [
>
> req=o.a.i.i.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest@43e45ce3
> ]
> java.lang.NullPointerException
>
> The full dump is in attachment.
>
> Since I am not authorized to create an issue in the repository I was
> using, I have to address my question to this list. If anybody involved
> in server-side implementation of best effort affinity is reading this,
> please tell me am I doing something wrong, or it is an actual bug? How
> can this issue be resolved?
>
> [1] https://github.com/gridgain/apache-ignite/tree/ignite-iep23
>

[Dmitry Melnichuk]

Igor,

Thank you! It helped. I adapted my code to the new protocol, so my
tests are passing.

On Tue, 2019-02-19 at 13:22 +0300, Igor Sapego wrote:

> This is my branch. I fixed an issue so re-merge and check if it
> helps.
>
> Best Regards,
> Igor
>
>
> On Tue, Feb 19, 2019 at 8:14 AM Dmitry Melnichuk <
> [hidden email]> wrote:
>
> > Igniters,
> >
> > I am currently trying to teach my thin client (pyignite) a new
> > trick
> > called “Best effort affinity”.
> >
> > I have been told that this feature is being implemented in the
> > private
> > branch [1], so I checked it out, built it, and gave it a go.
> >
> > The handshake goes as expected, I have actually managed to read the
> > node UUID. But on any subsequent request the server disconnects and
> > shows the following on its console:
> >
> > [ERROR][client-connector-#60][ClientListenerNioListener] Failed to
> > process client request [
> >
> > req=o.a.i.i.processors.platform.client.cache.ClientCacheGetOrCreateWithNameRequest@43e45ce3
> > ]
> > java.lang.NullPointerException
> >
> > The full dump is in attachment.
> >
> > Since I am not authorized to create an issue in the repository I
> > was
> > using, I have to address my question to this list. If anybody
> > involved
> > in server-side implementation of best effort affinity is reading
> > this,
> > please tell me am I doing something wrong, or it is an actual bug?
> > How
> > can this issue be resolved?
> >
> > [1] https://github.com/gridgain/apache-ignite/tree/ignite-iep23
> >