From 276946c915702c5ee30c0c5b8fe93cbe1fa664dc Mon Sep 17 00:00:00 2001 From: James M <35449344+JMercerGit@users.noreply.github.com> Date: Fri, 13 Dec 2024 12:40:09 +0000 Subject: [PATCH] General doc updates (#276) * Merge dev into master (#238) * Add CS 3.0.1 docs (#221) * Remove latest aliases from 3.0.0 * Remove latest aliases from 2.1.2 * Update download metadata 2023-08-16 * Add 3.0.1 * Update project descriptions * Make nav menu image link to version homepage * Added OTP version to CS 3.0.1 homepage * Added OTP version to CS 3.0.0. homepage * Hide titles for plaintext, text and log codeblocks * Fix headings * Hide codeblock title if blank * Fixed headings and tables * Formatting fixes * Moved Release notes and changes Downloads icon * Added the TOC back * Added LUNR-based search (#226) * Add CS 3.0.1 docs (#221) (#223) * Remove latest aliases from 3.0.0 * Remove latest aliases from 2.1.2 * Update download metadata 2023-08-16 * Add 3.0.1 * Update project descriptions * Make nav menu image link to version homepage * Added OTP version to CS 3.0.1 homepage * Added OTP version to CS 3.0.0. homepage * Hide titles for plaintext, text and log codeblocks * Fix headings * Hide codeblock title if blank * Fixed headings and tables * Formatting fixes * Moved Release notes and changes Downloads icon * Added the TOC back * Add "project" to community files * Add search index and test cases * Added search indexes to all projects and versions * Remove dead 3rd party tracking code * Replace search results screen * Replace search box * Add project_name_html to JSON * Added basic lunr search * Fix frontmatter issue * Fix quote issue * Removed Google Tag Manager stubs * Search improvements * Fix link * Fix link * Fix link and add search_boost * Add sample keywords and search boosts * Add example deprecated content. * Add keywords and boosts to search indexes * Add header meta value * Better layout and boost support * Auto-hide menu and move CSS * Added keywords * Added score * Updated CSS/JS * Add LUNR 2.3.9 JS file This was missed in the PR from pjac-search on 2023-09-01 as the `dynamic/js/vendor` folder is in the git.ignore file. * Update running-a-cluster.md (#228) * Update running-a-cluster.md * Update running-a-cluster.md * Updated Alpine Linux instuctions (#237) Added missing pages for 3.0.12+ Updated all to have correct URLs Updated 3.0.09-32.0.11 to have -r1 instead of -r0 Updated downloads template to show x86_64 and aarch64 available Updated 3.0.9+ to show Alpine Linux version and architecture * Various issues with riak-admin changes and search files fixed (#235) (#236) * Fixes broken links as a result of riak-admin/riak admin changes Fixes broken links as a result of riak-admin/riak admin changes * leveled_ko/so context leveled_ko/so context, closes #234 * Removes errant search files Pesky search references that got missed previously have been eliminated. This fixes #225 Co-authored-by: James M <35449344+JMercerGit@users.noreply.github.com> * Command Examples update (#230) (#239) Authored-by: James M <35449344+JMercerGit@users.noreply.github.com> Command output examples. * Fix for outdated references and changes to the upgrading checklist to remove basho support references (#240) (#241) * Resolves a broken link in a few pages after riak admin changes Resolves a broken link in a few pages after riak admin changes Also closes issue #220 * Changes to the upgrading checklist to remove references to basho support Changes to the upgrading checklist to remove references to Basho support and adds both community and TI Tokyo options. Also updates example emails in SI files from basho.com to dev.com Fixes issue #219 * Adds correct exampledomain usage Adds correct exampledomain usage Co-authored-by: James M <35449344+JMercerGit@users.noreply.github.com> * Version History updates for V2.0.0 - V2.9.10 (#242) * Version History updates for V2.0.0 - V2.9.10 Version History updates for V2.0.0 - V2.9.10 * Removed some remnant search files Removed some remnant search files * Fixes missing curl examples (#243) (#245) * Fixes missing curl examples (#243) Fixes missing curl examples * missing curl example (#246) * Fixes missing curl examples Fixes missing curl examples * 2.9.0p5 curl examples 2.9.0p5 curl examples that vanished into space * 3.0.8 curl fix (#247) * Fixes missing curl examples Fixes missing curl examples * 2.9.0p5 curl examples 2.9.0p5 curl examples that vanished into space * 3.0.8 curl example 3.0.8 curl example --------- Co-authored-by: James M <35449344+JMercerGit@users.noreply.github.com> --------- Co-authored-by: James M <35449344+JMercerGit@users.noreply.github.com> * Remove duplicate (#260) * Remove duplicate (#261) * Fix merge conflicts * Update Dockerfile * Update Alpine install instructions Update Alpine install instructions - This closes issue #255 * Updates deprecated mount option for performance configuration Updates deprecated mount option for performance configuration - This closes #273 * Fixes duplicate section of CRUD docs for Java Fixes duplicate section of CRUD docs for Java which closes issue #92 * Adds a note about OTP versions for CS and KV This should resolve issue #268 (Subject to discussion) * Update Release notes to correct a mistaken version number in a link Update Release notes to correct a mistaken version number in a link for 2.2.3 - closes issue #218 * Updating install files to remove references to installing source packages that are not available anymore. Closes issue #141 --------- Co-authored-by: Peter Clark --- content/riak/cs/2.1.2/cookbooks/installing.md | 4 ++++ content/riak/cs/3.0.0/cookbooks/installing.md | 4 ++++ content/riak/cs/3.0.1/cookbooks/installing.md | 4 ++++ .../getting-started/java/crud-operations.md | 18 ------------------ .../getting-started/java/crud-operations.md | 18 ------------------ .../getting-started/java/crud-operations.md | 18 ------------------ .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.2.3/release-notes.md | 2 +- .../getting-started/java/crud-operations.md | 18 ------------------ .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.9.0p5/using/performance.md | 4 +--- .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.9.1/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.9.10/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.9.2/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ content/riak/kv/2.9.4/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 13 ------------- content/riak/kv/2.9.7/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 13 ------------- content/riak/kv/2.9.8/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 13 ------------- content/riak/kv/2.9.9/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.1/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.1/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.10/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.10/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.10/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.11/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.11/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.11/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.12/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.12/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.12/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.13/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.13/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.13/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.14/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.14/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.14/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../3.0.15/setup/installing/alpine-linux.md | 12 +++++++----- .../riak/kv/3.0.15/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.15/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.16/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.16/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.2/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.2/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.3/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.3/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.4/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.4/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.6/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.6/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.7/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.7/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.0.8/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.8/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../kv/3.0.9/setup/installing/alpine-linux.md | 12 ++++++++---- .../riak/kv/3.0.9/setup/installing/source.md | 15 +-------------- content/riak/kv/3.0.9/using/performance.md | 6 +++--- .../getting-started/java/crud-operations.md | 18 ------------------ .../riak/kv/3.2.0/setup/installing/source.md | 15 +-------------- content/riak/kv/3.2.0/using/performance.md | 6 +++--- docker/Dockerfile | 19 ++++++++++++++----- 81 files changed, 163 insertions(+), 843 deletions(-) diff --git a/content/riak/cs/2.1.2/cookbooks/installing.md b/content/riak/cs/2.1.2/cookbooks/installing.md index dc03cebfab..6ff6267173 100644 --- a/content/riak/cs/2.1.2/cookbooks/installing.md +++ b/content/riak/cs/2.1.2/cookbooks/installing.md @@ -38,6 +38,10 @@ is built We strongly recommend using one of the documented [version combinations]({{}}riak/cs/2.1.2/cookbooks/version-compatibility/) when installing and running Riak CS. +>**Note on OTP version** +> +> **If version of OTP installed with Riak CS is a higher version then the OTP version installed with Riak KV a failure to read BEAM file will occur, therefore it should be ensured that the OTP versions match. + ## Installing Riak KV Before installing Riak CS, Riak KV must be installed on each node in diff --git a/content/riak/cs/3.0.0/cookbooks/installing.md b/content/riak/cs/3.0.0/cookbooks/installing.md index 77eb8179ac..4cd7e1d470 100644 --- a/content/riak/cs/3.0.0/cookbooks/installing.md +++ b/content/riak/cs/3.0.0/cookbooks/installing.md @@ -38,6 +38,10 @@ is built We strongly recommend using one of the documented [version combinations]({{}}riak/cs/3.0.0/cookbooks/version-compatibility/) when installing and running Riak CS. +>**Note on OTP version** +> +> **If version of OTP installed with Riak CS is a higher version then the OTP version installed with Riak KV a failure to read BEAM file will occur, therefore it should be ensured that the OTP versions match. + ## Installing Riak KV Before installing Riak CS, Riak KV must be installed on each node in diff --git a/content/riak/cs/3.0.1/cookbooks/installing.md b/content/riak/cs/3.0.1/cookbooks/installing.md index e47c4eab72..2b52877764 100644 --- a/content/riak/cs/3.0.1/cookbooks/installing.md +++ b/content/riak/cs/3.0.1/cookbooks/installing.md @@ -38,6 +38,10 @@ is built We strongly recommend using one of the documented [version combinations]({{}}riak/cs/3.0.1/cookbooks/version-compatibility/) when installing and running Riak CS. +>**Note on OTP version** +> +> **If version of OTP installed with Riak CS is a higher version then the OTP version installed with Riak KV a failure to read BEAM file will occur, therefore it should be ensured that the OTP versions match. + ## Installing Riak KV Before installing Riak CS, Riak KV must be installed on each node in diff --git a/content/riak/kv/2.2.0/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.2.0/developing/getting-started/java/crud-operations.md index 87a681801c..73808e48b0 100644 --- a/content/riak/kv/2.2.0/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.2.0/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.2.0/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.2.0/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.2.0/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.2.0/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.2.1/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.2.1/developing/getting-started/java/crud-operations.md index 8556b19540..7c6455dd56 100644 --- a/content/riak/kv/2.2.1/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.2.1/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.2.1/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.2.1/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.2.1/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.2.1/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.2.2/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.2.2/developing/getting-started/java/crud-operations.md index 1a938744b6..8b5179da84 100644 --- a/content/riak/kv/2.2.2/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.2.2/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.2.2/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.2.2/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.2.2/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.2.2/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.2.3/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.2.3/developing/getting-started/java/crud-operations.md index 469bf502c5..8ba1f5605e 100644 --- a/content/riak/kv/2.2.3/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.2.3/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.2.3/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.2.3/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.2.3/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.2.3/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.2.3/release-notes.md b/content/riak/kv/2.2.3/release-notes.md index 34816ee41f..2df7b002f4 100644 --- a/content/riak/kv/2.2.3/release-notes.md +++ b/content/riak/kv/2.2.3/release-notes.md @@ -30,4 +30,4 @@ In fixing a `riak` and `riak-admin` [issue](https://github.com/basho/node_packag ## Previous Release Notes -Please see the KV 2.2.2 release notes [here]({{}}riak/kv/2.2.3/release-notes/), and the KV 2.2.1 release notes [here]({{}}riak/kv/2.2.3/release-notes/). +Please see the KV 2.2.2 release notes [here]({{}}riak/kv/2.2.2/release-notes/), and the KV 2.2.1 release notes [here]({{}}riak/kv/2.2.1/release-notes/). diff --git a/content/riak/kv/2.2.6/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.2.6/developing/getting-started/java/crud-operations.md index 00a96aa653..db3d46f50e 100644 --- a/content/riak/kv/2.2.6/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.2.6/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.2.6/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.2.6/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.2.6/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.2.6/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.0p5/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.0p5/developing/getting-started/java/crud-operations.md index 84db1b76df..413ce6447a 100644 --- a/content/riak/kv/2.9.0p5/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.0p5/developing/getting-started/java/crud-operations.md @@ -82,24 +82,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.0p5/developing/usage/updat and [Conflict Resolution]({{}}riak/kv/2.9.0p5/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.9.0p5/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.9.0p5/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.0p5/using/performance.md b/content/riak/kv/2.9.0p5/using/performance.md index 419cafeccc..c954abc08e 100644 --- a/content/riak/kv/2.9.0p5/using/performance.md +++ b/content/riak/kv/2.9.0p5/using/performance.md @@ -169,9 +169,7 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.1/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.1/developing/getting-started/java/crud-operations.md index 820d3648ef..4b52bd94e6 100644 --- a/content/riak/kv/2.9.1/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.1/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.1/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.1/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.9.1/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.9.1/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.1/using/performance.md b/content/riak/kv/2.9.1/using/performance.md index 96932c5c65..97a3194853 100644 --- a/content/riak/kv/2.9.1/using/performance.md +++ b/content/riak/kv/2.9.1/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.10/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.10/developing/getting-started/java/crud-operations.md index e6724c7499..733242a23a 100644 --- a/content/riak/kv/2.9.10/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.10/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.10/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/2.9.10/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.9.10/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.9.10/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.10/using/performance.md b/content/riak/kv/2.9.10/using/performance.md index ba0cf236e3..b7bd77f41c 100644 --- a/content/riak/kv/2.9.10/using/performance.md +++ b/content/riak/kv/2.9.10/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.2/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.2/developing/getting-started/java/crud-operations.md index 2bb1910d81..48e0e969ff 100644 --- a/content/riak/kv/2.9.2/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.2/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.2/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.2/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.9.2/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.9.2/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.2/using/performance.md b/content/riak/kv/2.9.2/using/performance.md index 8690c1a716..cfa49d1076 100644 --- a/content/riak/kv/2.9.2/using/performance.md +++ b/content/riak/kv/2.9.2/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.4/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.4/developing/getting-started/java/crud-operations.md index f35398fba8..3709866f3b 100644 --- a/content/riak/kv/2.9.4/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.4/developing/getting-started/java/crud-operations.md @@ -74,24 +74,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.4/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.4/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/2.9.4/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/2.9.4/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/2.9.4/using/performance.md b/content/riak/kv/2.9.4/using/performance.md index 8972de50fb..b0800ce185 100644 --- a/content/riak/kv/2.9.4/using/performance.md +++ b/content/riak/kv/2.9.4/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.7/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.7/developing/getting-started/java/crud-operations.md index 1a25bca94b..f65312cc88 100644 --- a/content/riak/kv/2.9.7/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.7/developing/getting-started/java/crud-operations.md @@ -75,19 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.7/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.7/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - For more in depth information on updating objects and sibling resolution in Riak, see [Updating Objects]({{}}riak/kv/2.9.7/developing/usage/updating-objects/) and [Conflict Resolution]({{}}riak/kv/2.9.7/developing/usage/conflict-resolution/) diff --git a/content/riak/kv/2.9.7/using/performance.md b/content/riak/kv/2.9.7/using/performance.md index 331667f4c1..a291152000 100644 --- a/content/riak/kv/2.9.7/using/performance.md +++ b/content/riak/kv/2.9.7/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.8/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.8/developing/getting-started/java/crud-operations.md index 5e27fd3917..aabc1ce4b3 100644 --- a/content/riak/kv/2.9.8/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.8/developing/getting-started/java/crud-operations.md @@ -75,19 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.8/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.8/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - For more in depth information on updating objects and sibling resolution in Riak, see [Updating Objects]({{}}riak/kv/2.9.8/developing/usage/updating-objects/) and [Conflict Resolution]({{}}riak/kv/2.9.8/developing/usage/conflict-resolution/) diff --git a/content/riak/kv/2.9.8/using/performance.md b/content/riak/kv/2.9.8/using/performance.md index a46cb3b815..87104455c7 100644 --- a/content/riak/kv/2.9.8/using/performance.md +++ b/content/riak/kv/2.9.8/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/2.9.9/developing/getting-started/java/crud-operations.md b/content/riak/kv/2.9.9/developing/getting-started/java/crud-operations.md index e685da62b1..4c516823da 100644 --- a/content/riak/kv/2.9.9/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/2.9.9/developing/getting-started/java/crud-operations.md @@ -75,19 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/2.9.9/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/2.9.9/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - For more in depth information on updating objects and sibling resolution in Riak, see [Updating Objects]({{}}riak/kv/2.9.9/developing/usage/updating-objects/) and [Conflict Resolution]({{}}riak/kv/2.9.9/developing/usage/conflict-resolution/) diff --git a/content/riak/kv/2.9.9/using/performance.md b/content/riak/kv/2.9.9/using/performance.md index d2de2a332e..32bfefc7b9 100644 --- a/content/riak/kv/2.9.9/using/performance.md +++ b/content/riak/kv/2.9.9/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.1/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.1/developing/getting-started/java/crud-operations.md index b72b188b52..db90ce1933 100644 --- a/content/riak/kv/3.0.1/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.1/developing/getting-started/java/crud-operations.md @@ -76,24 +76,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.1/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.1/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.1/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.1/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.1/setup/installing/source.md b/content/riak/kv/3.0.1/setup/installing/source.md index bb185e44fb..9054bfbca1 100644 --- a/content/riak/kv/3.0.1/setup/installing/source.md +++ b/content/riak/kv/3.0.1/setup/installing/source.md @@ -54,20 +54,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.1/riak-3.0.1.tar.gz -tar zxvf riak-3.0.1.tar.gz -cd riak-3.0.1 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.1/using/performance.md b/content/riak/kv/3.0.1/using/performance.md index 98e5a9d629..40bf84e476 100644 --- a/content/riak/kv/3.0.1/using/performance.md +++ b/content/riak/kv/3.0.1/using/performance.md @@ -163,9 +163,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.10/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.10/developing/getting-started/java/crud-operations.md index 46a869165d..e535ddaf31 100644 --- a/content/riak/kv/3.0.10/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.10/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.10/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.10/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.10/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.10/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.10/setup/installing/alpine-linux.md b/content/riak/kv/3.0.10/setup/installing/alpine-linux.md index 2cc85411b2..34f2aefc70 100644 --- a/content/riak/kv/3.0.10/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.10/setup/installing/alpine-linux.md @@ -41,12 +41,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.10.0-r1` diff --git a/content/riak/kv/3.0.10/setup/installing/source.md b/content/riak/kv/3.0.10/setup/installing/source.md index 2aff2bfaa7..fc8a567663 100644 --- a/content/riak/kv/3.0.10/setup/installing/source.md +++ b/content/riak/kv/3.0.10/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.10/riak-3.0.10.tar.gz -tar zxvf riak-3.0.10.tar.gz -cd riak-3.0.10 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.10/using/performance.md b/content/riak/kv/3.0.10/using/performance.md index c73dceef66..b9ac242c98 100644 --- a/content/riak/kv/3.0.10/using/performance.md +++ b/content/riak/kv/3.0.10/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.11/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.11/developing/getting-started/java/crud-operations.md index cbe60c2d7e..ed9ae10303 100644 --- a/content/riak/kv/3.0.11/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.11/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.11/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.11/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.11/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.11/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.11/setup/installing/alpine-linux.md b/content/riak/kv/3.0.11/setup/installing/alpine-linux.md index e7402b0406..6d06e4e096 100644 --- a/content/riak/kv/3.0.11/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.11/setup/installing/alpine-linux.md @@ -41,12 +41,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.11.0-r1` diff --git a/content/riak/kv/3.0.11/setup/installing/source.md b/content/riak/kv/3.0.11/setup/installing/source.md index 0ceea074b8..b636eee167 100644 --- a/content/riak/kv/3.0.11/setup/installing/source.md +++ b/content/riak/kv/3.0.11/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.11/riak-3.0.11.tar.gz -tar zxvf riak-3.0.11.tar.gz -cd riak-3.0.11 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.11/using/performance.md b/content/riak/kv/3.0.11/using/performance.md index eee89da5f1..a67dd54d00 100644 --- a/content/riak/kv/3.0.11/using/performance.md +++ b/content/riak/kv/3.0.11/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.12/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.12/developing/getting-started/java/crud-operations.md index fa8ae7b8b8..2d5cf041e0 100644 --- a/content/riak/kv/3.0.12/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.12/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.12/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.12/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.12/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.12/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.12/setup/installing/alpine-linux.md b/content/riak/kv/3.0.12/setup/installing/alpine-linux.md index cc4bb00247..c5b50bd9c6 100644 --- a/content/riak/kv/3.0.12/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.12/setup/installing/alpine-linux.md @@ -41,12 +41,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages:: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.12.0-r0` diff --git a/content/riak/kv/3.0.12/setup/installing/source.md b/content/riak/kv/3.0.12/setup/installing/source.md index c33c02a798..30be47539e 100644 --- a/content/riak/kv/3.0.12/setup/installing/source.md +++ b/content/riak/kv/3.0.12/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.12/riak-3.0.12.tar.gz -tar zxvf riak-3.0.12.tar.gz -cd riak-3.0.12 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.12/using/performance.md b/content/riak/kv/3.0.12/using/performance.md index cdcbe61645..a6649e04b5 100644 --- a/content/riak/kv/3.0.12/using/performance.md +++ b/content/riak/kv/3.0.12/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.13/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.13/developing/getting-started/java/crud-operations.md index 0c0c9fa698..2e48d5fb6f 100644 --- a/content/riak/kv/3.0.13/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.13/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.13/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.13/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.13/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.13/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.13/setup/installing/alpine-linux.md b/content/riak/kv/3.0.13/setup/installing/alpine-linux.md index 846b5e71f8..38bb87edae 100644 --- a/content/riak/kv/3.0.13/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.13/setup/installing/alpine-linux.md @@ -41,12 +41,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.13.0-r0` diff --git a/content/riak/kv/3.0.13/setup/installing/source.md b/content/riak/kv/3.0.13/setup/installing/source.md index 1dd0386d1e..9d41bfe94d 100644 --- a/content/riak/kv/3.0.13/setup/installing/source.md +++ b/content/riak/kv/3.0.13/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.13/riak-3.0.13.tar.gz -tar zxvf riak-3.0.13.tar.gz -cd riak-3.0.13 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.13/using/performance.md b/content/riak/kv/3.0.13/using/performance.md index 374861e8d8..af7065513a 100644 --- a/content/riak/kv/3.0.13/using/performance.md +++ b/content/riak/kv/3.0.13/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.14/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.14/developing/getting-started/java/crud-operations.md index 27e92aa028..285ce31370 100644 --- a/content/riak/kv/3.0.14/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.14/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.14/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.14/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.14/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.14/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.14/setup/installing/alpine-linux.md b/content/riak/kv/3.0.14/setup/installing/alpine-linux.md index 85edf0b8df..36e9c84c8e 100644 --- a/content/riak/kv/3.0.14/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.14/setup/installing/alpine-linux.md @@ -41,12 +41,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.14.0-r0` diff --git a/content/riak/kv/3.0.14/setup/installing/source.md b/content/riak/kv/3.0.14/setup/installing/source.md index d76c3a86ca..65b5a43437 100644 --- a/content/riak/kv/3.0.14/setup/installing/source.md +++ b/content/riak/kv/3.0.14/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.14/riak-3.0.14.tar.gz -tar zxvf riak-3.0.14.tar.gz -cd riak-3.0.14 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source ### Installing from GitHub diff --git a/content/riak/kv/3.0.14/using/performance.md b/content/riak/kv/3.0.14/using/performance.md index 03f3e7733c..9a8188e115 100644 --- a/content/riak/kv/3.0.14/using/performance.md +++ b/content/riak/kv/3.0.14/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.15/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.15/developing/getting-started/java/crud-operations.md index cefae242b1..ffc40352d5 100644 --- a/content/riak/kv/3.0.15/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.15/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.15/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.15/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.15/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.15/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.15/setup/installing/alpine-linux.md b/content/riak/kv/3.0.15/setup/installing/alpine-linux.md index 7cda6ac33b..d0a871a83c 100644 --- a/content/riak/kv/3.0.15/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.15/setup/installing/alpine-linux.md @@ -43,12 +43,14 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: 1. Add the Riak repository: - * Run `echo https://files.tiot.jp/alpine/v3.16/main >> /etc/apk/repositories` -2. Download and install the Riak repository public key: - * Run `wget http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O /etc/apk/keys/alpine@tiot.jp.rsa.pub` -3. Update your list of packages: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -4. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.15.0-r0` diff --git a/content/riak/kv/3.0.15/setup/installing/source.md b/content/riak/kv/3.0.15/setup/installing/source.md index e81ea6d0f1..e6d8148399 100644 --- a/content/riak/kv/3.0.15/setup/installing/source.md +++ b/content/riak/kv/3.0.15/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.15/riak-3.0.15.tar.gz -tar zxvf riak-3.0.15.tar.gz -cd riak-3.0.15 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.15/using/performance.md b/content/riak/kv/3.0.15/using/performance.md index dbadc6fd5b..a4759214dc 100644 --- a/content/riak/kv/3.0.15/using/performance.md +++ b/content/riak/kv/3.0.15/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.16/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.16/developing/getting-started/java/crud-operations.md index ad7e03519f..75ad96f6c7 100644 --- a/content/riak/kv/3.0.16/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.16/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.16/developing/usage/updati and [Conflict Resolution]({{}}riak/kv/3.0.16/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.16/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.16/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.16/setup/installing/source.md b/content/riak/kv/3.0.16/setup/installing/source.md index a0bf757409..21397302fc 100644 --- a/content/riak/kv/3.0.16/setup/installing/source.md +++ b/content/riak/kv/3.0.16/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.16/riak-3.0.16.tar.gz -tar zxvf riak-3.0.16.tar.gz -cd riak-3.0.16 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.16/using/performance.md b/content/riak/kv/3.0.16/using/performance.md index c7ce846358..b66d2a05ed 100644 --- a/content/riak/kv/3.0.16/using/performance.md +++ b/content/riak/kv/3.0.16/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.2/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.2/developing/getting-started/java/crud-operations.md index f5fcd0ccab..f960862a6b 100644 --- a/content/riak/kv/3.0.2/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.2/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.2/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.2/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.2/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.2/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.2/setup/installing/source.md b/content/riak/kv/3.0.2/setup/installing/source.md index b7bc962f6c..a921a6cef3 100644 --- a/content/riak/kv/3.0.2/setup/installing/source.md +++ b/content/riak/kv/3.0.2/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.2/riak-3.0.2.tar.gz -tar zxvf riak-3.0.2.tar.gz -cd riak-3.0.2 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.2/using/performance.md b/content/riak/kv/3.0.2/using/performance.md index 4ae20ee099..8c58d5946f 100644 --- a/content/riak/kv/3.0.2/using/performance.md +++ b/content/riak/kv/3.0.2/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.3/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.3/developing/getting-started/java/crud-operations.md index bf67bbd1ec..d39650cb2e 100644 --- a/content/riak/kv/3.0.3/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.3/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.3/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.3/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.3/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.3/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.3/setup/installing/source.md b/content/riak/kv/3.0.3/setup/installing/source.md index 61e428c533..482264f024 100644 --- a/content/riak/kv/3.0.3/setup/installing/source.md +++ b/content/riak/kv/3.0.3/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.3/riak-3.0.3.tar.gz -tar zxvf riak-3.0.3.tar.gz -cd riak-3.0.3 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.3/using/performance.md b/content/riak/kv/3.0.3/using/performance.md index 68a5af045f..af8e0a178a 100644 --- a/content/riak/kv/3.0.3/using/performance.md +++ b/content/riak/kv/3.0.3/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.4/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.4/developing/getting-started/java/crud-operations.md index 69b0f34e4e..81f5301ab5 100644 --- a/content/riak/kv/3.0.4/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.4/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.4/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.4/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.4/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.4/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.4/setup/installing/source.md b/content/riak/kv/3.0.4/setup/installing/source.md index 596e116bab..89c1ffe305 100644 --- a/content/riak/kv/3.0.4/setup/installing/source.md +++ b/content/riak/kv/3.0.4/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.4/riak-3.0.4.tar.gz -tar zxvf riak-3.0.4.tar.gz -cd riak-3.0.4 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.4/using/performance.md b/content/riak/kv/3.0.4/using/performance.md index dc6355b16f..06f863eee6 100644 --- a/content/riak/kv/3.0.4/using/performance.md +++ b/content/riak/kv/3.0.4/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.6/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.6/developing/getting-started/java/crud-operations.md index e90566f4b2..217ee7befe 100644 --- a/content/riak/kv/3.0.6/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.6/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.6/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.6/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.6/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.6/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.6/setup/installing/source.md b/content/riak/kv/3.0.6/setup/installing/source.md index 208bd1af82..13f495158f 100644 --- a/content/riak/kv/3.0.6/setup/installing/source.md +++ b/content/riak/kv/3.0.6/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.6/riak-3.0.6.tar.gz -tar zxvf riak-3.0.6.tar.gz -cd riak-3.0.6 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.6/using/performance.md b/content/riak/kv/3.0.6/using/performance.md index e445b1b577..344db96d05 100644 --- a/content/riak/kv/3.0.6/using/performance.md +++ b/content/riak/kv/3.0.6/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.7/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.7/developing/getting-started/java/crud-operations.md index 6cc05b8379..0c0cc1a7a5 100644 --- a/content/riak/kv/3.0.7/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.7/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.7/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.7/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.7/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.7/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.7/setup/installing/source.md b/content/riak/kv/3.0.7/setup/installing/source.md index 5b76918c39..4662d61cac 100644 --- a/content/riak/kv/3.0.7/setup/installing/source.md +++ b/content/riak/kv/3.0.7/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.7/riak-3.0.7.tar.gz -tar zxvf riak-3.0.7.tar.gz -cd riak-3.0.7 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.7/using/performance.md b/content/riak/kv/3.0.7/using/performance.md index cb7484c765..c8c8587e2c 100644 --- a/content/riak/kv/3.0.7/using/performance.md +++ b/content/riak/kv/3.0.7/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.8/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.8/developing/getting-started/java/crud-operations.md index 13da2a8327..dc2da9b739 100644 --- a/content/riak/kv/3.0.8/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.8/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.8/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.8/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.8/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.8/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.8/setup/installing/source.md b/content/riak/kv/3.0.8/setup/installing/source.md index 6bea257cf1..aef64d87da 100644 --- a/content/riak/kv/3.0.8/setup/installing/source.md +++ b/content/riak/kv/3.0.8/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.8/riak-3.0.8.tar.gz -tar zxvf riak-3.0.8.tar.gz -cd riak-3.0.8 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.8/using/performance.md b/content/riak/kv/3.0.8/using/performance.md index df002a989f..0976a19d01 100644 --- a/content/riak/kv/3.0.8/using/performance.md +++ b/content/riak/kv/3.0.8/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.0.9/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.0.9/developing/getting-started/java/crud-operations.md index 57c214faec..1d38539d7a 100644 --- a/content/riak/kv/3.0.9/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.0.9/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.0.9/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.0.9/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.0.9/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.0.9/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.0.9/setup/installing/alpine-linux.md b/content/riak/kv/3.0.9/setup/installing/alpine-linux.md index ccbb7d00dc..b0b065228d 100644 --- a/content/riak/kv/3.0.9/setup/installing/alpine-linux.md +++ b/content/riak/kv/3.0.9/setup/installing/alpine-linux.md @@ -40,11 +40,15 @@ The following steps have been tested to work with Riak KV on: To install Riak on Alpine Linux: -1. Add the Alpine Edge repository: - * Run `echo https://dl-cdn.alpinelinux.org/alpine/edge/testing >> /etc/apk/repositories` -2. Update your list of packages: +1. Add the Riak repository: + * Run `sudo echo "https://files.tiot.jp/alpine/v3.16/main" >> /etc/apk/repositories` +2. Change directory to place the repository key: + * Run `cd /etc/apk/keys/` +3. Download and install the Riak repository public key: + * Run `sudo curl http://files.tiot.jp/alpine/alpine@tiot.jp.rsa.pub -O` +4. Update your list of packages: * Run `apk update` -3. Install Riak: +5. Install Riak: * For the latest version, run `apk add riak` * For a specific version, run `apk add riak=3.0.9.0-r1` diff --git a/content/riak/kv/3.0.9/setup/installing/source.md b/content/riak/kv/3.0.9/setup/installing/source.md index da9c01e246..0f77886da3 100644 --- a/content/riak/kv/3.0.9/setup/installing/source.md +++ b/content/riak/kv/3.0.9/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.0.9/riak-3.0.9.tar.gz -tar zxvf riak-3.0.9.tar.gz -cd riak-3.0.9 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.0.9/using/performance.md b/content/riak/kv/3.0.9/using/performance.md index 49a97b7ae2..240b47591f 100644 --- a/content/riak/kv/3.0.9/using/performance.md +++ b/content/riak/kv/3.0.9/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/content/riak/kv/3.2.0/developing/getting-started/java/crud-operations.md b/content/riak/kv/3.2.0/developing/getting-started/java/crud-operations.md index 36ddd9a117..0ec8d1827c 100644 --- a/content/riak/kv/3.2.0/developing/getting-started/java/crud-operations.md +++ b/content/riak/kv/3.2.0/developing/getting-started/java/crud-operations.md @@ -75,24 +75,6 @@ Riak, see [Updating Objects]({{}}riak/kv/3.2.0/developing/usage/updatin and [Conflict Resolution]({{}}riak/kv/3.2.0/developing/usage/conflict-resolution/) documentation. -## Updating Objects - -Once we've read the object back in from Riak, we can update the object -and store it back as we did before with the `StoreValue` object: - -```java -fetchedObject.setValue(BinaryValue.create("You can be my wingman any time.")); -StoreValue updateOp = new StoreValue.Builder(fetchedObject) - .withLocation(quoteObjectLocation) - .build(); -StoreValue.Response updateOpResp = client.execute(updateOp); -``` - -For more in depth information on updating objects and sibling resolution in -Riak, see [Updating Objects]({{}}riak/kv/3.2.0/developing/usage/updating-objects/) -and [Conflict Resolution]({{}}riak/kv/3.2.0/developing/usage/conflict-resolution/) -documentation. - ## Deleting Objects Now that we've stored and then fetched the object, we can delete it by diff --git a/content/riak/kv/3.2.0/setup/installing/source.md b/content/riak/kv/3.2.0/setup/installing/source.md index 572282f813..2bb444728a 100644 --- a/content/riak/kv/3.2.0/setup/installing/source.md +++ b/content/riak/kv/3.2.0/setup/installing/source.md @@ -53,20 +53,7 @@ compiler is [GCC](https://gcc.gnu.org/). ## Installation The following instructions generate a complete, self-contained build of -Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the unpacked -or cloned source. - -### Installing from source package - -Download the Riak source package from the [Download Center][downloads] and build: - -```bash -curl -O https://files.tiot.jp/riak/kv/3.0/3.2.0/riak-3.2.0.tar.gz -tar zxvf riak-3.2.0.tar.gz -cd riak-3.2.0 -make locked-deps -make rel -``` +Riak in `$RIAK/rel/riak` where `$RIAK` is the location of the cloned source. ### Installing from GitHub diff --git a/content/riak/kv/3.2.0/using/performance.md b/content/riak/kv/3.2.0/using/performance.md index d47161ae06..c65ae05a0c 100644 --- a/content/riak/kv/3.2.0/using/performance.md +++ b/content/riak/kv/3.2.0/using/performance.md @@ -162,9 +162,9 @@ multiple nodes holding the same data, these two options can be changed to boost I/O performance. We recommend setting `barrier=0` and `data=writeback` when using the ext4 filesystem. -Similarly, the XFS file system defaults can be optimized to improve -performance. We recommend setting `nobarrier`, `logbufs=8`, -`logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +Similarly, the XFS file system defaults can be optimized to improve performance. +We recommend setting `logbufs=8`, `logbsize=256k`, and `allocsize=2M` when using the XFS filesystem. +In addition, up to Ubuntu 17.10 and RHEL/CentOS 7.9 (and any OS using a Linux kernel before 4.15) we recommend setting `nobarrier`. As with the `noatime` setting, these settings should be added to `/etc/fstab` so that they are persisted across server restarts. diff --git a/docker/Dockerfile b/docker/Dockerfile index e6c6839bc2..cace1ea705 100644 --- a/docker/Dockerfile +++ b/docker/Dockerfile @@ -1,8 +1,17 @@ -FROM ruby:alpine +FROM ruby:2.7-alpine +ENV LIBV8_VERSION 3.16.14.16 LABEL description="Alpine + Ruby + Hugo Docker container." LABEL maintainer="Peter Clark " +RUN apk add --update --no-cache libstdc++ && \ + apk add --update --no-cache --virtual build-deps build-base make git bash && \ + apk add --update --no-cache --virtual python3 && \ + gem install libv8 + ## && \ +## gem install therubyracer && \ +## apk del build-deps + # taken from jojomi/docker-hugo at https://github.com/jojomi/docker-hugo/blob/0.25.1/Dockerfile COPY ./run.sh /run.sh RUN chmod u+x /run.sh @@ -24,12 +33,12 @@ RUN tar -xf /tmp/hugo_${HUGO_VERSION}_Linux-64bit.tar.gz -C /tmp \ RUN apk add --no-cache ca-certificates # add stuff to allow ruby to compile native extentions -RUN apk -U add --no-cache gcc musl-dev make g++ git build-base clang \ - && rm -rf /var/cache/apk/* -ENV CXX=clang++ +#RUN apk -U add --no-cache gcc musl-dev make g++ git build-base clang \ +# && rm -rf /var/cache/apk/* +#ENV CXX=clang++ # add stuff to make mini_racer work -RUN gem install 'specific_install' +#RUN gem install 'specific_install' #RUN gem specific_install -l "https://github.com/sagarjauhari/mini_racer" # pre-install commonnly used items