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
LTL is not displayed after applying #11623 in some instance #11643
Comments
Did you by any change try to |
It seems like the federated timeline works as fast as before... It is specifically the query for the local timeline that is much slower... Local timeline query:
Compared to federated timeline query:
|
The follow index reduces the query time back to 0.133 ms: add_index :statuses, [:id, :account_id], name: :index_statuses_on_local, where: '(local OR (uri IS NULL)) AND deleted_at IS NULL AND visibility = 0 AND reblog_of_id IS NULL AND ((NOT reply) OR (in_reply_to_account_id = account_id))', algorithm: :concurrently, order: { id: :desc } |
Gargron
added a commit
that referenced
this issue
Aug 23, 2019
Gargron
added a commit
that referenced
this issue
Aug 24, 2019
hiyuki2578
pushed a commit
to ProjectMyosotis/mastodon
that referenced
this issue
Oct 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behaviour
After applying #11623, LTL of my instance ( taruntarun.net ) can no longer be displayed with “504 gateway timeout”.
Currently it is operating normally.
I have temporarily restored to the state before #11623.
But, for my other two instances, there is no problem.
Maybe some PostgreSQL task was working.
These are my DB server load graphs.
I ran
assets:precompile
anddb:migrate
at 15:05 - 15:10 JST.( At this point, I didn’t run
tootctl cache clear
. )And at 15:10 - 15:12, I restarted mastodon with another VPS.
( My instance taruntarun.net is running
mastodon-*.service
and DB (PostgreSQL and Redis) on different VPS. )Then when I reloaded the web browser, LTL was not displayed.
After that, “504 gateway timeout” was displayed.
Then, the CPU usage and disk access of DB servers have increased rapidly.
Then I stopped
mastodon-*.service
again and rantootctl cache clear
.And I re-run
mastodon-*.service
, but the situation did not improve.Then, I ran
rake db:rollback
.About 2 hours later (not on the graph) I stopped
mastodon-*service
and PostgreSQL.After that I returned the code to the state before #11623. Now it works fine.
Specifications
Equivalent to master branch 4ef8d8b ( 6aefe60 )
The text was updated successfully, but these errors were encountered: