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

Move persisted cache configuration to metastore and introduce cache configuration versioning

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Currently, we persist cache configuration to local files which resulted in several inconsistencies when a node misses configuration update (create index, cache destroy, etc).

      I think the cache configuration should be saved to the metastore the same way as baseline topology is saved. Same mechanics should be used for conflicting configuration updates resolution.

      Along with cache configuration, it also makes sense to move marshaller and binary metadata to the metastore.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                agoncharuk Alexey Goncharuk
              • Votes:
                1 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

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