Skip to content

Conversation

@Josipmrden
Copy link
Contributor

Add best practice for helm upgrade.
Current version has a bug:

Defaulted container "memgraph-coordinator" out of: memgraph-coordinator, init (init), init-sysctl (init)
[2025-07-02 09:36:02.263] [warning] The auth-module-executable flag is deprecated and superseded by auth-module-mappings. To switch to the up-to-date flag, start Memgraph with auth-module-mappings=basic:{your module's path}.
[2025-07-02 09:36:02.263] [warning] The bolt_session_inactivity_timeout flag is deprecated. The feature has been removed, inactivity timeout is not supported as of v3.0.
[2025-07-02 09:36:02.263] [warning] storage_parallel_index_recovery flag is deprecated. Check storage_mode_parallel_schema_recovery for more details.
[2025-07-02 09:36:02.265] [warning] The auth-module-executable flag is deprecated and superseded by auth-module-mappings. To switch to the up-to-date flag, start Memgraph with auth-module-mappings=basic:{your module's path}.
[2025-07-02 09:36:02.265] [warning] The bolt_session_inactivity_timeout flag is deprecated. The feature has been removed, inactivity timeout is not supported as of v3.0.
[2025-07-02 09:36:02.265] [warning] storage_parallel_index_recovery flag is deprecated. Check storage_mode_parallel_schema_recovery for more details.
You are running Memgraph v3.3.0
To get started with Memgraph, visit https://memgr.ph/start
[2025-07-02 09:36:02.307] [memgraph_log] [info] config recover on startup true, flags true
[2025-07-02 09:36:02.364] [memgraph_log] [trace] Coordinator will be initialized using flags.
[2025-07-02 09:36:02.391] [memgraph_log] [info] Replication configuration will be stored and will be automatically restored in case of a crash.
[2025-07-02 09:36:02.391] [memgraph_log] [debug] Cannot find data needed for restore replication role in persisted metadata.
[2025-07-02 09:36:02.391] [memgraph_log] [trace] Creating coordinator state.
[2025-07-02 09:36:02.392] [memgraph_log] [trace] [RpcServer] register ShowInstancesReq -> ShowInstancesRes
[2025-07-02 09:36:02.392] [memgraph_log] [info] Starting 1 RPC workers
[2025-07-02 09:36:02.392] [memgraph_log] [info] RPC server is fully armed and operational
[2025-07-02 09:36:02.392] [memgraph_log] [info] RPC listening on 0.0.0.0:10000
[2025-07-02 09:36:02.421] [memgraph_log] [critical] Failed to deserialize snapshot with id: snapshot_id_5. Error: [json.exception.out_of_range.403] key 'cluster_state' not found
[json.exception.out_of_range.403] key 'cluster_state' not found

@Josipmrden Josipmrden self-assigned this Jul 2, 2025
github-merge-queue bot pushed a commit to memgraph/mage that referenced this pull request Aug 6, 2025
The main challenge with the HA cluster upgrade tests is that there are
multiple different things to wait for (helm, port-forward,
data/coordinator getting ready) -> it gets very complex very quickly.

## v3.4
- [x] Nested indices
- [x] Vector search on edges
- [x] Implement the k8s helm chart upgrade scenario
- [x] Resolve memgraph/memgraph#3023 (any
reuse of the PVCs failed)
- [x] memgraph/best-practices#43 -> almost
exactly the same, look at how the script is waiting for pods
- [x] Make upgrades more robust ->
https://www.notion.so/memgraph/How-to-make-upgrade-more-robust-1c26b158b98180a1a76cd8998e2e7ca4#1c36b158b98180f286d4eed383d1451a
- [x] Add some other feature tests (expand test cases) -> skipped
- [x] Put a timeout to the wait_for_memgraph function (default is 10s)
- [x] Validate results / make sure to exit on errors / properly name /
refactor Python scripts
- [x] Test for if main is elected specifically before running any CREATE
query on the cluster

NEXT >> #643

---------

Co-authored-by: antejavor <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant