-
Notifications
You must be signed in to change notification settings - Fork 654
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
Massive user creation issues #3859
Comments
Previous link, it's a great explanation of what's happening here: @Kartones , @lbosque: currently we enable UPDATE: I've just known this is not only for onpremise but also for Sass, which makes the role assignment alternative much better, IMHO |
yes, role assignment would be much better. Also no need to stop DBs or do special config on them as with the toast. |
Ok, I'm on it (role assignment) right now, since grant also creates performance problems: Central creation script, which triggers a request to box per user, makes creation fail because of timeout on the same grant:
|
Ok, first fix solved 1091-limit. Next on 2243:
|
Org deletion takes ages because of permission revoking, which seems to grow exponentially. This trace is repeated thousands of times:
|
Next limit, 2265:
query: " GRANT SELECT ON "public"."geometry_columns" TO "cartodb_publicuser_0c60dec6-f74c-4d65-9a03-318abb306287" " |
Next limit, 2267:
query: |
Next, 2443:
query: "GRANT ALL ON SCHEMA "cdb_importer" TO "development_cartodb_user_169ca77f-6f95-4d9e-a0f4-134e85611e9a"" |
Next: permission error inserting in shared table through sql api:
UPDATE: if you set an explicit value for cartodb_id it works. Sequence permission is a previous bug ans has been reported in CartoDB/CartoDB-SQL-API#230. |
User 1091 creation failed because "GRANT SELECT ON ALL TABLES IN SCHEMA "public" TO "development_cartodb_user_7d7d7501-6ac4-4f1f-9c72-89fd72c8159d"" query (line) triggered this error: PG::Error: ERROR: row is too big: size 8168, maximum size 8160. Relevant backtrace:
"/vagrant/app/models/user.rb:2016:in
run_queries_in_transaction'", "/vagrant/app/models/user.rb:1611:in
set_user_privileges_in_public_schema'","/vagrant/app/models/user.rb:1674:in
set_user_privileges'", "/vagrant/app/models/user.rb:1539:in
setup_schema'","/vagrant/app/models/user.rb:1506:in
setup_organization_user'", "/vagrant/app/models/user.rb:1691:in
setup_user'","/vagrant/app/models/user.rb:142:in `after_create'"
Problem explaination & workaround found.
Permission granting is a bigger issue than expected, this issue groups all:
CASCADE
atdatabase.run(%Q{ DROP SCHEMA IF EXISTS "#{self.database_schema}" CASCADE })
(drop_organization_user
method, see PR comments).The text was updated successfully, but these errors were encountered: