Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using --experimental-enabled=text-search with old mg_lib prevents startup #1945

Open
dhawleyGadzoom opened this issue Apr 16, 2024 · 1 comment
Labels
bug bug community community Effort - Unknown Effort - Unknown Frequency - EveryTime Frequency - EveryTime Reach - VeryFew Reach - VeryFew Severity - S1 Severity - S1

Comments

@dhawleyGadzoom
Copy link

Memgraph version
docker image memgraph/memgraph-mage:1.16-memgraph-2.16

Environment
Controlled by docker-compose.yml

Describe the bug
When I enable --experimental-enabled=text-search in docker-compose.yml and replace the old container (but not the mg_lib volume), the new container fails to start up. It gives the message "Tried to retrieve an unknown database "memgraph"."

To Reproduce
Steps to reproduce the behavior in a very minimal way:

  1. Run the following docker-compose.yml (docker-compose up)
version: '3.3'
services:
  memgraph:
    image: memgraph/memgraph-mage:1.16-memgraph-2.16
    ports:
      - "7687:7687"
      - "7444:7444"
    command: []
    volumes:
      - mg_lib_1:/var/lib/memgraph
      - mg_log_1:/var/log/memgraph
      - mg_etc_1:/etc/memgraph
volumes:
  mg_lib_1:
  mg_lib_2:
  mg_log_1:
  mg_etc_1:
  1. Delete the container
  2. Run the following docker-compose.yml (docker-compose up). Note that this is the same as the above except with command --experimental-enabled=text-search
version: '3.3'
services:
  memgraph:
    image: memgraph/memgraph-mage:1.16-memgraph-2.16
    ports:
      - "7687:7687"
      - "7444:7444"
    command: ["--experimental-enabled=text-search"]
    volumes:
      - mg_lib_1:/var/lib/memgraph
      - mg_log_1:/var/log/memgraph
      - mg_etc_1:/etc/memgraph
volumes:
  mg_lib_1:
  mg_lib_2:
  mg_log_1:
  mg_etc_1:

At this point, I the docker-compose up command prints memgraph_1 exited with code 139 and the container (which is now stopped) ends its logs with Tried to retrieve an unknown database "memgraph".

Expected behavior
I expect the container from step 3 to start up and stay running. If there were any existing data in mg_lib_1 (like there is for my actual, non minimally reproducible setup), then I would expect to be able to use the experimental text search on the existing data.

Logs
Full log of memgraph container:

[2024-04-15 20:23:52.974] [warning] storage_parallel_index_recovery flag is deprecated. Check storage_mode_parallel_schema_recovery for more details.
2024-04-15T20:23:52.974709812Z [2024-04-15 20:23:52.974] [warning] auth_module_create_missing_role flag is deprecated. It not possible to create roles through the module anymore.
2024-04-15T20:23:52.974713015Z [2024-04-15 20:23:52.974] [warning] auth_module_create_missing_user flag is deprecated. It not possible to create users through the module anymore.
2024-04-15T20:23:52.974715320Z [2024-04-15 20:23:52.974] [warning] auth_module_manage_roles flag is deprecated. It not possible to create roles through the module anymore.
2024-04-15T20:23:52.974717589Z [2024-04-15 20:23:52.974] [warning] storage_parallel_index_recovery flag is deprecated. Check storage_mode_parallel_schema_recovery for more details.
2024-04-15T20:23:52.974721436Z [2024-04-15 20:23:52.974] [warning] auth_module_create_missing_role flag is deprecated. It not possible to create roles through the module anymore.
2024-04-15T20:23:52.974723799Z [2024-04-15 20:23:52.974] [warning] auth_module_create_missing_user flag is deprecated. It not possible to create users through the module anymore.
2024-04-15T20:23:52.974725901Z [2024-04-15 20:23:52.974] [warning] auth_module_manage_roles flag is deprecated. It not possible to create roles through the module anymore.
2024-04-15T20:23:53.001705737Z You are running Memgraph v2.16.0
2024-04-15T20:23:53.001763565Z To get started with Memgraph, visit https://memgr.ph/start
2024-04-15T20:23:53.039990284Z Tried to retrieve an unknown database "memgraph".
2024-04-15T20:23:53.040015150Z 

Additional context
Note that the container starts fine if it's using a new mg_lib volume. For example, after running the steps detailed above to reproduce the bug, I am able to start a container just fine with the following (the same but using the mg_lib_2 volume instead of mg_lib_1):

version: '3.3'
services:
  memgraph:
    image: memgraph/memgraph-mage:1.16-memgraph-2.16
    ports:
      - "7687:7687"
      - "7444:7444"
    command: ["--experimental-enabled=text-search"]
    volumes:
      - mg_lib_2:/var/lib/memgraph
      - mg_log_1:/var/log/memgraph
      - mg_etc_1:/etc/memgraph
volumes:
  mg_lib_1:
  mg_lib_2:
  mg_log_1:
  mg_etc_1:

If I understand correctly, this means that in order to use the text search with my existing data, I would need to export the data, switch volumes, and import the data, which is not ideal.

@dhawleyGadzoom dhawleyGadzoom added the bug bug label Apr 16, 2024
@antejavor antejavor added Severity - S1 Severity - S1 Effort - Unknown Effort - Unknown Frequency - EveryTime Frequency - EveryTime Reach - VeryFew Reach - VeryFew community community labels Apr 18, 2024
@antejavor
Copy link
Contributor

Hi @dhawleyGadzoom, thanks for opening the issue and describing it.

We will take a look into this and get back to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bug community community Effort - Unknown Effort - Unknown Frequency - EveryTime Frequency - EveryTime Reach - VeryFew Reach - VeryFew Severity - S1 Severity - S1
Projects
Development

No branches or pull requests

2 participants