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

Topology aware Raft client creates its own message handler which is not aware of Raft group

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0
    • None

    Description

      Topology aware client creates its own message handler for leader change notifications. These notifications does not contain group ids, which is a problem for adding such clients for partition replication groups. Moreover, having same message handlers for one type of messages in number that is equal to the count of topology aware clients seems not to be a good decision and leads to weird problems after adding topology aware clients for partition Raft groups, which appear as random integration tests fails. 

      We should get rid of this handler in topology aware client and create dedicated message processor in RPC.

      Attachments

        Issue Links

          Activity

            People

              Denis Chudov Denis Chudov
              Denis Chudov Denis Chudov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 0.5h
                  0.5h