Re: [Gluster-users] GlusterFS and Kafka

2017-05-25 Thread Raghavendra Talur
On Thu, May 25, 2017 at 8:39 PM, Joe Julian wrote: > Maybe hooks? Yes, we were thinking of the same :) Christopher, Gluster has hook-scripts facility that admins can write and set those to be run on certain events in Gluster. We have a event for volume creation. Here are

Re: [Gluster-users] Failure while upgrading gluster to 3.10.1

2017-05-25 Thread Atin Mukherjee
On Thu, 25 May 2017 at 19:11, Pawan Alwandi wrote: > Hello Atin, > > Yes, glusterd on other instances are up and running. Below is the > requested output on all the three hosts. > > Host 1 > > # gluster peer status > Number of Peers: 2 > > Hostname: 192.168.0.7 > Uuid:

Re: [Gluster-users] GlusterFS and Kafka

2017-05-25 Thread Joe Julian
Maybe hooks? On May 25, 2017 6:48:04 AM PDT, Christopher Schmidt wrote: >Hi Humble, > >thanks for that, it is really appreciated. > >In the meanwhile, using K8s 1.5, what can I do to disable the >performance >translator that doesn't work with Kafka? Maybe something while

Re: [Gluster-users] GlusterFS and Kafka

2017-05-25 Thread Humble Chirammal
Hi Christopher, We are experimenting few other options to get rid of this issue. We will provide an update as soon as we have it. On Thu, May 25, 2017 at 7:18 PM, Christopher Schmidt wrote: > Hi Humble, > > thanks for that, it is really appreciated. > > In the meanwhile,

Re: [Gluster-users] Fwd: Re: VM going down

2017-05-25 Thread Alessandro Briosi
Il 25/05/2017 15:24, Joe Julian ha scritto: > You'd want to see the client log. I'm not sure where proxmox > configures those to go. > > On May 24, 2017 11:57:33 PM PDT, Alessandro Briosi > wrote: > > Il 19/05/2017 17:27, Alessandro Briosi ha scritto: >> Il 12/05/2017

Re: [Gluster-users] GlusterFS and Kafka

2017-05-25 Thread Christopher Schmidt
Hi Humble, thanks for that, it is really appreciated. In the meanwhile, using K8s 1.5, what can I do to disable the performance translator that doesn't work with Kafka? Maybe something while generating the Glusterfs container for Kubernetes? Best Christopher Humble Chirammal

Re: [Gluster-users] Fwd: Re: VM going down

2017-05-25 Thread Alessandro Briosi
Il 25/05/2017 15:24, Joe Julian ha scritto: > You'd want to see the client log. I'm not sure where proxmox > configures those to go. This is all the content of glusterfs/cli.log (previous file cli.log.1 is from 5 days ago) [2017-05-25 06:21:30.736837] I [cli.c:728:main] 0-cli: Started running

Re: [Gluster-users] Failure while upgrading gluster to 3.10.1

2017-05-25 Thread Pawan Alwandi
Hello Atin, Yes, glusterd on other instances are up and running. Below is the requested output on all the three hosts. Host 1 # gluster peer status Number of Peers: 2 Hostname: 192.168.0.7 Uuid: 5ec54b4f-f60c-48c6-9e55-95f2bb58f633 State: Peer in Cluster (Disconnected) Hostname: 192.168.0.6

Re: [Gluster-users] Fwd: Re: VM going down

2017-05-25 Thread Joe Julian
You'd want to see the client log. I'm not sure where proxmox configures those to go. On May 24, 2017 11:57:33 PM PDT, Alessandro Briosi wrote: >Il 19/05/2017 17:27, Alessandro Briosi ha scritto: >> Il 12/05/2017 12:09, Alessandro Briosi ha scritto: You probably should

Re: [Gluster-users] Distributed re-balance issue

2017-05-25 Thread Nithya Balachandran
On 24 May 2017 at 22:54, Mahdi Adnan wrote: > Well yes and no, when i start the re-balance and check it's status, it > just tells me it completed the re-balance, but it really did not move any > data and the volume is not evenly distributed. > > right now brick6 is full,

Re: [Gluster-users] GlusterFS and Kafka

2017-05-25 Thread Raghavendra Talur
On Thu, May 25, 2017 at 11:21 AM, Christopher Schmidt wrote: > So this change of the Gluster Volume Plugin will make it into K8s 1.7 or > 1.8. Unfortunately too late for me. > > Does anyone know how to disable performance translators by default? Humble, Do you know of any

Re: [Gluster-users] Fwd: Re: VM going down

2017-05-25 Thread Alessandro Briosi
Il 19/05/2017 17:27, Alessandro Briosi ha scritto: > Il 12/05/2017 12:09, Alessandro Briosi ha scritto: >>> You probably should open a bug so that we have all the troubleshooting >>> and debugging details in one location. Once we find the problem we can >>> move the bug to the right component. >>>