Skip to content

Conversation

schiessle
Copy link
Member

Don't try to connect to the lookup server if the lookup server was disabled
by the admin or an empty lookup server URL was given

fix #13396

Additionally we should consider to add a background job which clean existing data from the lookup sever once the admin disabled it, see #13396 (comment)

Don't try to connect to the lookup server if the lookup server was disabled
by the admin or an empty lookup server URL was given

Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
@MorrisJobke MorrisJobke added 3. to review Waiting for reviews bug labels Jan 7, 2019
@rullzer
Copy link
Member

rullzer commented Jan 29, 2019

@schiessle ping

Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
@schiessle
Copy link
Member Author

@rullzer from my pov this is ready to go in after my last commits from yesterday

@MorrisJobke MorrisJobke mentioned this pull request Mar 4, 2019
45 tasks
Copy link
Member

@MorrisJobke MorrisJobke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code makes sense 👍

@MorrisJobke
Copy link
Member

CI failure unrelated

Copy link
Member

@rullzer rullzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets do this then

@rullzer
Copy link
Member

rullzer commented Mar 14, 2019

Should we backport this? I guess it would make sense.

@MorrisJobke
Copy link
Member

/backport to stable15

@backportbot-nextcloud
Copy link

backport to stable15 in #14696

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lookup_server_connector creates a lot of oc_jobs entries, high DB load during cron, and tries to sync even if disabled in options
4 participants