Dmitry Rodionov
Dmitry Rodionov
@vadim2404 See #2784
Is it part of the https://github.com/neondatabase/neon/issues/2158? So I can pick it up, from there, right?
Now we use threadpool for background tasks: https://github.com/neondatabase/neon/pull/1933 Should we close this or we plan to deal with threads going from page_service as well?
Got another example https://neon-github-public-dev.s3.amazonaws.com/reports/pr-2710/release/3386856615/index.html#suites/82004ab4e3720b47bf78f312dabe7c55/7f6280bcd3ecab01/
Causing trouble again. Having quite a lot of `unable to lock pid file. could not daemonize. bailing.` errors here https://github.com/neondatabase/neon/runs/7690981632?check_suite_focus=true
Attach is no longer lost, still relevant for detach
1. Yep, this is still the case: ``` > curl -v -XPOST http://localhost:9898/v1/tenant/1acf99ebac07d01ea7abf3bd104e8e58/detach * Trying 127.0.0.1:9898... * Connected to localhost (127.0.0.1) port 9898 (#0) > POST /v1/tenant/1acf99ebac07d01ea7abf3bd104e8e58/detach HTTP/1.1 > Host:...
It will be 409 Conflict: Tenant X already exists
I agree with the analysis. It seems that the main issue was the absence of retried. However, I'm not sure that we can safely continue from interrupted detach operation. I...
As discussed moving to draft.