Memperbarui instance Looker yang dihosting pelanggan
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda akan diberi tahu tentang rilis Looker baru saat tersedia. Sebaiknya update Looker secara rutin untuk terus mendapatkan perbaikan bug dan fitur baru.
Jika memiliki cluster instance Looker, Anda harus mengupdate satu node sepenuhnya sebelum mengupdate instance lainnya.
Proses update ini mengasumsikan bahwa instance Looker Anda menyertakan skrip startup, yang seharusnya telah diinstal sebagai bagian dari proses penginstalan Looker awal.
Download rilis terbaru file JAR Looker seperti yang dijelaskan di halaman dokumentasi Mendownload File JAR Looker.
Hentikan proses Looker dari shell, sebagai pengguna looker:
sudo su - looker
cd /home/looker/looker
./looker stop
Jika Anda mengupdate cluster Looker, ulangi proses ini agar Looker dihentikan di setiap node.
Cadangkan seluruh direktori Looker, termasuk direktori tersembunyi (lihat halaman dokumentasi Memulihkan cadangan untuk mengetahui detail selengkapnya).
Mengganti nama looker-x.x.x.jar menjadi looker.jar dan looker-dependencies-x.x.x.jar menjadi looker-dependencies.jar. Salin looker.jar dan looker-dependencies.jar ke direktori server (/home/looker/looker/looker.jar). Kedua file harus berada di direktori yang sama.
Mulai proses Looker dari shell sebagai pengguna looker:
Jika Anda mengupdate cluster Looker, mulai proses Looker hanya di satu node. Jangan mulai Looker di node lain hingga node pertama menyelesaikan proses update.
./looker start
Anda juga dapat menggunakan perintah java -jar untuk memulai Looker. JAR inti akan menemukan JAR dependensi selama berada di direktori ./looker bersama dengan JAR inti.
Selain itu, jika lebih memilih untuk menggunakan skrip startup yang disediakan Looker, Anda dapat menemukan skrip startup di: https://github.com/looker/customer-scripts.
Saat Anda mengupdate versi Looker, Looker juga harus mengupdate database internalnya. Update database biasanya memerlukan waktu kurang dari lima menit, tetapi terkadang bisa lebih lama dari proses startup Looker. Jika Anda mencoba memulai Looker saat database internal masih diupdate, proses daemonizing akan habis waktunya dalam enam menit dengan pesan "Waktu tunggu Looker dimulai habis".
Selama update, migrasi yang diperlukan dapat memerlukan waktu hingga satu jam, terutama jika Anda melewati beberapa rilis. Jika Anda menerima pesan error ini, tunggu hingga update selesai dan Looker dimulai. Anda dapat mengonfirmasi apakah proses update masih berjalan menggunakan perintah:
ps -f $(pgrep -f -- '-jar looker.jar')
Menghentikan dan memulai ulang proses Looker saat pembaruan database internal sedang berlangsung dapat merusak database internal. Jika hal ini terjadi, pulihkan Looker dari cadangan yang ada dan lakukan update lagi.
Jika Anda mengupdate cluster Looker, tunggu hingga node pertama menyelesaikan proses update sebelum memulai Looker di node lain.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-31 UTC."],[],[],null,["# Updating a customer-hosted Looker instance\n\n| We strongly advise against using these instructions to roll back to an earlier version of Looker. This can cause serious problems that are tedious and difficult to recover from. Instead, we recommend that you [restore a backup](/looker/docs/restoring-backups) if you need to go back to an earlier version of Looker.\n\nYou will be notified of new Looker releases as they become available. We recommend updating Looker regularly to keep current with bug fixes and new features.\n\u003e If you have a [cluster](/looker/docs/clustering-looker) of Looker instances, you must update a single node completely before updating the other instances.\n\nThis update process assumes your Looker instance includes the startup script, which should have been installed as part of the [initial Looker installation process](/looker/docs/installing-looker-application).\n\n1. Download the most recent release of the Looker JAR files as described on the [Downloading the Looker JAR Files](/looker/docs/downloading-looker-jar-files) documentation page.\n2. Stop the Looker process from shell, as the **looker** user:\n\n sudo su - looker\n cd /home/looker/looker\n ./looker stop\n\n If you are updating a Looker cluster, repeat this process so that Looker is stopped on every node.\n3. Back up your entire Looker directory, including hidden directories (see the [Restoring backups](/looker/docs/restoring-backups) documentation page for more detail).\n\n4. If you have [migrated Looker's default in-memory database to an external MySQL database](/looker/docs/migrating-looker-backend-db-to-mysql), or if you are updating a Looker cluster, back up the MySQL database.\n\n5. Rename `looker-x.x.x.jar` to `looker.jar` and `looker-dependencies-x.x.x.jar` to `looker-dependencies.jar`. Copy `looker.jar` and `looker-dependencies.jar` to the server directory (`/home/looker/looker/looker.jar`). Both files *must* be in the same directory.\n\n6. Start the Looker process from the shell as the **looker** user:\n\n If you are updating a Looker cluster, start the Looker process on one node only. Do not start Looker on the other nodes until the first node has completed the update process. \n\n ./looker start\n\n You can also use the `java -jar` command to start Looker. The core JAR will find the dependency JAR as long as it is in the `./looker` directory along with the core JAR.\n\n In addition, if you'd rather use a Looker-provided startup script, you can find a startup script at: \u003chttps://github.com/looker/customer-scripts\u003e.\n\n When you update your Looker version, Looker must also update its internal database. The database update usually takes less than five minutes, but it can sometimes take longer than the Looker startup process. If you try to start Looker while the internal database is still updating, the daemonizing process will time out in six minutes with the message \"Timed out waiting for Looker to start.\"\n\n During an update, the required migrations can take up to an hour, especially if you are skipping several releases. If you receive this error message, wait for the update to finish and for Looker to start. You can confirm whether the update process is still running by using the command: \n\n ps -f $(pgrep -f -- '-jar looker.jar')\n\n Stopping and restarting the Looker process while the internal database updates are in progress can corrupt the internal database. If this happens, restore Looker from an existing backup and perform the update again.\n7. If you are updating a Looker cluster, wait until the first node has completed the update process before starting Looker on the other nodes."]]
