Skip to content

Lock not getting released during migrations #5

@azhar1038

Description

@azhar1038

When I try to run multiple edda apps at the same time, first app starts properly but second one fails with error saying schema_version table does not exists. I did some debugging and found that the second app is not able to acquire the lock. This happens because the first app is not releasing the lock properly. Reason is that release lock is happening in a different db connection than the one it was acquired.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions