Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-6579

WAL history does not used when node returns to cluster again

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • persistence
    • None

    Description

      When I have set big enough value to "WAL history size" and stop node on 20 minutes, I got the message from coordinator (order=1):

      2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
       cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2424, haveHistory=false]
      2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
       cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2427, haveHistory=false]
      2017-10-06 15:46:33.429 [WARN ][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl] Partition has been scheduled for rebalancing due to outdated update counter [nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
       cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2426, haveHistory=false]
      

      after start node again.
      I think, history size should be enough, but I see it is not by logs (haveHistory=false).

      Attachments

        Activity

          People

            Unassigned Unassigned
            v.pyatkov Vladislav Pyatkov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: