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.

Sign up for GitHub

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

Jump to bottom

DB transitions/migration system for server #4980

Open
JuniorJPDJ opened this issue May 9, 2021 · 7 comments · May be fixed by #6263
Open

DB transitions/migration system for server #4980

JuniorJPDJ opened this issue May 9, 2021 · 7 comments · May be fixed by #6263
Labels
feature-request This issue or PR deals with a new feature server

Comments

@JuniorJPDJ
Copy link
Contributor

Most of murmur admins start their server with SQLite, sometimes when server is growing, SQLite is not providing necessary performance and freezes server. It would be cool to have migration system for eg. migrating SQLite to PGSQL or MariaDB.

Workaroundish migration makes maintenance pain in ass and creates bugs like #4292

In #4292 @Krzmbrzl stated it would be cool to have it so I'm creating this issue to make it not disappear :D
@Krzmbrzl Krzmbrzl added feature-request This issue or PR deals with a new feature server labels May 9, 2021
@Krzmbrzl
Copy link
Member

Krzmbrzl commented May 9, 2021

The ToDo-list for the pending DB-rewrite keeps growing xD

@Kissaki
Copy link
Member

Kissaki commented May 9, 2021

When do you start seeing issues?

Sqlite runs entirely in memory, so really, the overhead is much smaller using it as a data storage. And with only a single process using the database, there is no need for db user access synchronization.

@JuniorJPDJ
Copy link
Contributor Author

@Kissaki doubt
I had problems with IO overload on my server and pgsql fixed the issue on mumble.
I also saw similar comments but for mariadb instead of sqlite.
I had to wait few seconds eg. when switching between channels.

@Krzmbrzl
Copy link
Member

I had to wait few seconds eg. when switching between channels.

Out of the top of my head I would say that for this action there is no DB access involved though

@JuniorJPDJ
Copy link
Contributor Author

JuniorJPDJ commented May 10, 2021 •
edited
Loading

I had to wait few seconds eg. when switching between channels.

Out of the top of my head I would say that for this action there is no DB access involved though

Well, keeping track of channel changes and last channel writes to DB afaik ;P
And.. practice shows other thing ;) moving to pgsql solved all problems.

Anyway: I think it's offtopic here.

@skobkin
Copy link

skobkin commented Jan 21, 2022

Out of the top of my head I would say that for this action there is no DB access involved though

Isn't murmur logging to the database too?

@Krzmbrzl
Copy link
Member

Isn't murmur logging to the database too?

Indeed, it is

@Krzmbrzl Krzmbrzl linked a pull request Nov 19, 2023 that will close this issue
Draft
1 task
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Jun 29, 2024
@Krzmbrzl
FEAT(server): JSON dump of database contents
5e4858f 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Jun 29, 2024
@Krzmbrzl
FEAT(server): JSON import/export to/from database
8077acf 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Jul 6, 2024
@Krzmbrzl
FEAT(server): JSON import/export to/from database
287608b 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Jul 6, 2024
@Krzmbrzl
FEAT(server): JSON import/export to/from database
acec29b 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Jul 13, 2024
@Krzmbrzl
FEAT(server): JSON import/export to/from database
1c58bd3 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Krzmbrzl added a commit to Krzmbrzl/mumble that referenced this issue Aug 20, 2024
@Krzmbrzl
FEAT(server): JSON import/export to/from database
c522c1b 
The dumped JSON format may not be 100% DB backend independent but it
should be somewhat close to it.

Implements mumble-voip#4980
Implements mumble-voip#2960 (must be done manually though)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request This issue or PR deals with a new feature server
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

WIP: Refactor server database Krzmbrzl/mumble
4 participants
@Kissaki @skobkin @JuniorJPDJ @Krzmbrzl