similar to: Heketi and Geo Replication.

Hello, I have a gluster cluster with 4 nodes, that is managed using heketi. I want to test the removeal of one node. We have several volumes on it, some with rep=2, others with rep=3. I get the following error: [root at CTYI1458 .ssh]# heketi-cli --user admin --secret "******" node remove 749850f8e5fd23cf6a224b7490499659 Error: Failed to remove device, error: Cannot replace brick

Hi This is gluster 3.8.4. Volume options are out of the box. Sharding is off (and I don't think enabling it would matter) I haven't done much performance tuning. For one thing, using a simple script that just creates files I can easily flood the network, so I don't expect a performance issue. The problem we see is that after a certain time the fuse clients completely stop accepting

Hi all, A few questions. - Is POSIX locking enabled when using the native client? I would assume yes. - What other settings/tuneables exist when it comes to file locking? Krist -- Vriendelijke Groet | Best Regards | Freundliche Gr??e | Cordialement ------------------------------ Krist van Besien | Senior Architect | Red Hat EMEA Cloud Practice | RHCE | RHCSA Open Stack @: krist at

Thanks for the suggestion, this solved it for us, and we probably found the cause as well. We had performance co-pilot running and it was continously enabling profiling on volumes... We found the reference to the node that had the lock, and restarted glusterd on that node, and all went well from there on. Krist On 31 May 2017 at 15:56, Vijay Bellur <vbellur at redhat.com> wrote: >

Hi all, I am trying to do trivial things, like setting quota, or just querying the status and keep getting "Another transaction is in progres for <some volume>" These messages pop up, then disappear for a while, then pop up again... What do these messages mean? How do I figure out which "transaction" is meant here, and what do I do about it? Krist -- Vriendelijke

Hi Krist, What are your volume options on that setup? Have you tried tuning it for the kind of workload and files size you have? I would definitely do some tests with feature.shard=on/off first. If shard is on, try playing with features.shard-block-size. Do you have jumbo frames (MTU=9000) enabled across the switch and nodes? if you have concurrent clients writing/reading, it could be beneficial

Hi all, I'm doing some performance test... If I test a simple sequential write using dd I get a thorughput of about 550 Mb/s. When I do a sequential write test using sysbench this drops to about 200. Is this due to the way sysbench tests? Or has in this case the performance of sysbench itself become the bottleneck? Krist -- Vriendelijke Groet | Best Regards | Freundliche Gr??e |

Hi all, Trying to do some availability testing. We have three nodes: node1, node2, node3. Volumes are all replica 2, across all three nodes. As a test we disconnected node1, buy removing the vlan tag for that host on the switch it is connected to. As a result node2 and node3 now show node1 in disconnected status, and show the volumes as degraded. This is ecpected. However logging in to node1

Hi all, I usualy advise clients to use the native client if at all possible, as it is very robust. But I am running in to problems here. In this case the gluster system is used to store video streams. Basicaly the setup is the following: - A gluster cluster of 3 nodes, with ample storage. They export several volumes. - The network is 10GB, switched. - A "recording server" which

On Thu, Aug 24, 2017 at 9:01 AM, Krist van Besien <krist at redhat.com> wrote: > Hi > This is gluster 3.8.4. Volume options are out of the box. Sharding is off > (and I don't think enabling it would matter) > > I haven't done much performance tuning. For one thing, using a simple > script that just creates files I can easily flood the network, so I don't >

Hi Talur, I've successfully got Gluster deployed as a DaemonSet using k8s spec file glusterfs-daemonset.json from https://github.com/heketi/heketi/tree/master/extras/kubernetes but then when I try deploying heketi using heketi-deployment.json spec file, I end up with a CrashLoopBackOff pod. # kubectl get pods NAME READY STATUS RESTARTS AGE

Hi Bishoy, Adding Talur who can help address your queries on Heketi. @wattsteve's github repo on glusterfs-kubernetes is a bit dated. You can either refer to gluster/gluster-kubernetes or heketi/heketi for current documentation and operational procedures. Regards, Vijay On Fri, Jul 21, 2017 at 2:19 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi, > > I'm

Hi, I'm trying to deploy Gluster and Heketi on a Kubernetes cluster I'm following the guide at https://github.com/gluster/gluster-kubernetes/ but the video referenced in the page is showing json files used while the git repo has only yaml files, they are quiet similar though, but Gluster is a deployment not a DaemonSet. I deploy Gluster DaemonSet successfully, but heketi is giving me the

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I

Heketi v5.0.1 is now available. This release[1] fixes a flaw that was found in heketi API that permits issuing of OS commands through specially crafted requests, possibly leading to escalation of privileges. More details can be obtained at CVE-2017-15103. [2] If authentication is turned "on" in heketi configuration, the flaw can be exploited only by those who possess authentication

Hi all, Heketi v6.0.0 is now available [1]. This is the new stable version of Heketi. Older versions are discontinued. The main additions in this release are the block-volume API, a great deal of stabilization to prevent inconsistent database and out-of-sync situations, and tooling to do disaster recovery when the database is bad. Changelog * Add support for gluster-block volumes * Add device

Hi, I have the following setup in place: 1 node : RancherOS having Rancher application for Kubernetes setup 2 nodes : RancherOS having Rancher agent 1 node : CentOS 7 workstation having kubectl installed and folder cloned/downloaded from https://github.com/gluster/gluster-kubernetes using which i run Heketi setup (gk-deploy -g) I also have rancher-glusterfs-server container running with

Hello, I have the following problem: On a solaris 10 machine, with 5 "zones" there is a process that is talking to the wrong db server. I need to find out which process this is, so I can analize this further. I have tried to doing this using tcpsnoop from the DTrace toolkit, but without success. This is what I''ve done. First I started tcpsnoop, dumping it''s output

That is certainly OK, but you can also just use print(ggsurvplot(...)) as your final statement. out <- RFS( ...) would then return the ggsurvplot object *and* graph it. Any good R tutorial or a web search will provide more details on function returns, which you might find useful. Cheers, Bert Bert Gunter "The trouble with having an open mind is that people keep coming along and

Thank you, your suggestion is simpler and logically better. I had impression that the last object in a function gets returned, so I did not add the print function at the bottom line of the function definition. Returning an object and graph the object are different process, I am a beginner for writing R function and need to find a good guide source about writing R functions. If you know a good