aboutsummaryrefslogtreecommitdiff
path: root/public/the-strange-case-of-elasticsearch-allocation-failure.html
diff options
context:
space:
mode:
authorMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 10:17:43 +0100
committerMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 10:17:43 +0100
commitae24d9a8869c497537839f330384cbadb2cf687c (patch)
tree79184f1d1db6f0b8e2f7aad3a262b3a2bccdde58 /public/the-strange-case-of-elasticsearch-allocation-failure.html
parent409dfae3983b55ffa469a556683fab4ec70b1e99 (diff)
downloadmitjafelicijan.com-ae24d9a8869c497537839f330384cbadb2cf687c.tar.gz
Updated theme
Diffstat (limited to 'public/the-strange-case-of-elasticsearch-allocation-failure.html')
-rwxr-xr-xpublic/the-strange-case-of-elasticsearch-allocation-failure.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/public/the-strange-case-of-elasticsearch-allocation-failure.html b/public/the-strange-case-of-elasticsearch-allocation-failure.html
index dcaa7ce..51bd8d1 100755
--- a/public/the-strange-case-of-elasticsearch-allocation-failure.html
+++ b/public/the-strange-case-of-elasticsearch-allocation-failure.html
@@ -59,11 +59,11 @@ dropped the original one with the following command.<pre tabindex=0 style=backgr
59</span></span></code></pre><p>On the surface it looks like all is working but I have a long road in front of 59</span></span></code></pre><p>On the surface it looks like all is working but I have a long road in front of
60me to get all the things working again. Cluster now shows that it is in Green 60me to get all the things working again. Cluster now shows that it is in Green
61mode but I am also getting a notification that the cluster has processing status 61mode but I am also getting a notification that the cluster has processing status
62which could mean million of things.<p>Godspeed!</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNotDirectoryToFilesystem target=_blank rel=noopener>One reason that ZFS can't turn a directory into a filesystem</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>One of the wishes that I and other people frequently have for ZFS 62which could mean million of things.<p>Godspeed!</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns
63is the ability to take an existing directory (and everything 63a lock on a Linux NFS server, which turned
64underneath it) in a ZFS filesystem and turn it into a sub-filesystem 64out to be specific to NFS v3 (which I really should have seen coming,
65of its own. One reason for wanting this is that a number of things 65since it involved NLM and lockd). Finding the NFS v4 client that
66are set and controlled on a per-filesyst…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen 66owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
67and Bradley Kuhn, are interacting on the OSI's license-discuss 67and Bradley Kuhn, are interacting on the OSI's license-discuss
68list where the're doing 68list where the're doing
69bad computer history and insisting that a guy Larry Rosen 69bad computer history and insisting that a guy Larry Rosen