GridGain Community Edition

Expand all | Collapse all

No support for affinity in GridGain whereas Apache provides

  • 1.  No support for affinity in GridGain whereas Apache provides

    Posted 07-13-2020 05:48 AM
      |   view attached

    Hi Team,

    Apache Ignite supports affinity with zero backups whereas GridGain doesn't seem to do so.

    Nodes and partitions that were brought down in GridGain were lost and data is not retrievable whereas in Apache Ignite everything worked fine with no extra configuration.

    I've documented the set up and steps for the same. Please check and clarify.

    Objective - Verifying the data collocation with affinity key, backups as 0 is intentional just to see if functionality is working.

    In production cases it would be a number > 1. 

    Also,

    1. Does Ignite support the custom affinity key for collocating data using more than one field?
    2. Are partition policies supported in GridGain different from those supported in Apache Ignite?

    ------------------------------
    Saikiran Boppudi
    SSE
    Nisum
    ------------------------------

    Attachment(s)



  • 2.  RE: No support for affinity in GridGain whereas Apache provides

    Posted 07-14-2020 04:03 AM
    Hello!

    Persistent clusters operate with READ_WRITE_SAFE PartitionLossPolicy by default:
    https://www.gridgain.com/docs/latest/developers-guide/partition-loss-policy?#configuring-partition-loss-policy

    This means that operations on partitions which were lost for some time, need their partition loss status reset when baseline nodes come back, You can do that with control.sh utility:
    bin/control.sh --cache reset_lost_partitions SQL_CITY_CACHE

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 3.  RE: No support for affinity in GridGain whereas Apache provides

    Posted 07-14-2020 04:05 AM
    With regards to multi-field affinity, while you could do that (by putting @AffinityKeyMapped annotation on a complex object), this will require all participating caches to have affinity on all these columns, so this is usually not what users want.​

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------



  • 4.  RE: No support for affinity in GridGain whereas Apache provides

    Posted 07-14-2020 05:17 AM
    Thanks Ilya Kasnacheev,

    It worked in my local machine.

    Is there an option to set this automatically? For a real time production scenario?

    Can do we set it to automatic trigger?

    Thanks for the info


    ------------------------------
    Saikiran Boppudi
    SSE
    Nisum
    ------------------------------



  • 5.  RE: No support for affinity in GridGain whereas Apache provides

    Posted 07-14-2020 06:02 AM
    Hello!

    You can reset partition loss status via API and you can listen for such events, so you can set up some automation. Please see the referenced documentation page.

    Regards,

    ------------------------------
    Ilya Kasnacheev
    Community Support Specialist
    GridGain
    ------------------------------