Bug 764206 (GLUSTER-2474)

Created attachment 443

We got 2 clients and one server.
We open the same db in the 2 clients -> sqlite /mnt/glusterfs/test.db
In this db we got a table t1.
in the the first client we do an insert on t1 -> insert into t1.
In the second client we do a select, the row inserted in the first client is not here.
If we quit then reopen sqlite on the second client and do the select again, the new row is here.

(In reply to comment #0)
> We got 2 clients and one server.
> We open the same db in the 2 clients -> sqlite /mnt/glusterfs/test.db
> In this db we got a table t1.
> in the the first client we do an insert on t1 -> insert into t1.
> In the second client we do a select, the row inserted in the first client is
> not here.
> If we quit then reopen sqlite on the second client and do the select again, the
> new row is here.

hi,
   I saw the volfiles. They are not standard volume file configurations. The gluster 3.1.2 comes with CLI to create the volumes of your choice. You dont have to edit any volfiles manually.

Could you please refer to http://europe.gluster.org/community/documentation/index.php/Gluster_3.1_Filesystem_Installation_and_Configuration_Guide

for setting up the volumes you intend to. Please let me know how it goes.

Pranith.

(In reply to comment #3)
> (In reply to comment #0)
> > We got 2 clients and one server.
> > We open the same db in the 2 clients -> sqlite /mnt/glusterfs/test.db
> > In this db we got a table t1.
> > in the the first client we do an insert on t1 -> insert into t1.
> > In the second client we do a select, the row inserted in the first client is
> > not here.
> > If we quit then reopen sqlite on the second client and do the select again, the
> > new row is here.
> 
> hi,
>    I saw the volfiles. They are not standard volume file configurations. The
> gluster 3.1.2 comes with CLI to create the volumes of your choice. You dont
> have to edit any volfiles manually.
> 
> Could you please refer to
> http://europe.gluster.org/community/documentation/index.php/Gluster_3.1_Filesystem_Installation_and_Configuration_Guide
> 
> for setting up the volumes you intend to. Please let me know how it goes.
> 
> Pranith.

The client vol-file does not contain any replicate translator.

volume remote1
  type protocol/client
  option transport-type tcp/client
  option remote-host 192.168.30.160
  option transport.socket.remote-port 6996
  option remote-subvolume brick
end-volume

Please use the gluster CLI to create the replicated volume. The instructions are mentioned in the wiki link in the previous comment.

(In reply to comment #3)
> (In reply to comment #0)
> > We got 2 clients and one server.
> > We open the same db in the 2 clients -> sqlite /mnt/glusterfs/test.db
> > In this db we got a table t1.
> > in the the first client we do an insert on t1 -> insert into t1.
> > In the second client we do a select, the row inserted in the first client is
> > not here.
> > If we quit then reopen sqlite on the second client and do the select again, the
> > new row is here.
> hi,
>    I saw the volfiles. They are not standard volume file configurations. The
> gluster 3.1.2 comes with CLI to create the volumes of your choice. You dont
> have to edit any volfiles manually.
> Could you please refer to
> http://europe.gluster.org/community/documentation/index.php/Gluster_3.1_Filesystem_Installation_and_Configuration_Guide
> for setting up the volumes you intend to. Please let me know how it goes.
> Pranith.

Hi,
thanks for your reply,
my colleague is in holiday this week,
he will test that next week.

Please update about the status of this bug. I will have to mark it invalid in case the procedure in creating the volumes is wrong. I will wait for one more week for this, In case you dont reply, I will assume that it is indeed because of the problem in procedure.

Pranith

Hello, 
We have not precise that we used virtual machines on ubuntu 10.10 on vmware workstation environment.
Our configuration we have modified was for gluster 2.0. But we have tested with gluster 3.0 and the CLI.
We have the same results.


Next, we test without virtualization on simple machines on ubuntu 10.10 and this test have success.

I think this bug is about gluster with vmware.

(In reply to comment #7)
> Hello, 
> We have not precise that we used virtual machines on ubuntu 10.10 on vmware
> workstation environment.
> Our configuration we have modified was for gluster 2.0. But we have tested with
> gluster 3.0 and the CLI.
> We have the same results.
> 
> 
> Next, we test without virtualization on simple machines on ubuntu 10.10 and
> this test have success.
> 
> I think this bug is about gluster with vmware.

Virtual machines should not be a problem. I do my daily tests on VMs. Could you try your tests with 3.1.4/3.2.0 with the gluster CLI. In your comments you mentioned you did it with 3.0. I just want to make sure that you tried with either 3.1.4 or 3.2.0.

Pranith.

Finaly, we have resolved this bug.
We updated sqlite3 version to 3.7.2.

Thank you for your help.