[Chainquery] Upgrade from mysql TCP connections to direct .socket connection. #63
Labels
No labels
Accepted
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
help wanted
icebox
In Review
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-docker#63
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Share socket from the mariadb container with the chainquery container via volumes then connect directly.
@nikooo777 mentioned in a slack message that we should be using
mysql.socket
viamysqldsn="lbry:PASSWORD@unix(/var/run/mysqld/mysqld.sock)/chainquery"
in the Chainquery configurator start.shUsing a direct socket connection will require testing but should vastly improve query speeds and security.
It should support socket and TCP, as socket cannot be used in multi-host setups.
Why MariaDB btw? In production we use perconaDB.
Any considerable improvements?
Also if it's not easy to achieve we can stick to TCP, the speed improvements are minimal.
@nikooo777 I've been testing with MySQL 5.7 (not MariaDB)
https://github.com/lbryio/lbry-docker/blame/master/contrib/systemd-cloud-init.md#L97
I can test with perconaDB, is there a specific version I should use?
Thanks for the reminder @nikooo777 I've opened a PR for a Percona swap. #69