This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Knowledge DropLast tested: This is caused by trying to run Looker
version 7.14 or earlier with a newer Java version that isn't supported
yet. Make sure the jar is Looker version 7.16+ you're using Java 9+, or
downgrade Java to JDK
8https://docs.looke...
Knowledge DropLast tested: Apr 10, 2020 This error generally means that
Looker tried to have the Chromium process load a page in order to
capture its contents in a PDF or PNG, but the page did not fire the
DOMContentLoaded event within 5 minutes. Thi...
Knowledge DropLast tested: Mar 18, 2020 This error will happen if Looker
loses communication with Chromium while it's rendering a PNG. The most
common cause of this is Chromium not having enough resources to run, and
can be especially bad in containe...
Knowledge DropLast tested: Feb 4, 2020 The custodian in 7.2+ is meant to
automatically find schedules that are stuck in a state that they cannot
recover from and mark them as complete with an error message. It will
not affect any schedules that are a...
Knowledge DropLast tested: Oct 24, 2018 You can Command+Shift+click on
the gear menu for the visualization to download a .json file with the
visualization settings metadata for a particular visualization.This
content is subject to limited support.
The best option would be to line up the history IDs in the SQL context
comments with the history IDs in the system activity history explore,
using the dashboard fields and the History ID.
@thomas_brittain for the separate scheduler and render setup, the
complete list of flags to add to the nodes behind the LB would
be:--scheduler-threads=0 --unlimited-scheduler-threads=0
--concurrent-render-caching-jobs=0 --concurrent-render-jobs=0The...