I was able to get the docker containers I'm using to test with to
install the latest builds from gluster.org.
So client/server versions are both 3.13.2
I am testing two main cases, both using sqlite3. With a php program
wrapping all database operations with an flock(), it now works as
expected. I
On Tue, Mar 6, 2018 at 10:58 PM, Raghavendra Gowdappa
wrote:
>
>
> On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson wrote:
>
>> Raghavendra,
>>
>> I've commited my tests case to https://github.com/powool/gluster.git -
>> it's grungy, and a work in progress, but I am happy to take change
>> suggest
On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson wrote:
> Raghavendra,
>
> I've commited my tests case to https://github.com/powool/gluster.git -
> it's grungy, and a work in progress, but I am happy to take change
> suggestions, especially if it will save folks significant time.
>
> For the rest,
Raghavendra,
I've commited my tests case to https://github.com/powool/gluster.git -
it's grungy, and a work in progress, but I am happy to take change
suggestions, especially if it will save folks significant time.
For the rest, I'll reply inline below...
On Mon, Mar 5, 2018 at 10:39 PM, Raghave
On 2018-03-06, Amar Tumballi wrote:
>> If anyone would like our test scripts, I can either tar them up and
>> email them or put them in github - either is fine with me. (they rely
>> on current builds of docker and docker-compose)
>>
>>
> Sure, sharing the test cases makes it very easy for us to s
Adding csaba
On Tue, Mar 6, 2018 at 9:09 AM, Raghavendra Gowdappa
wrote:
> +Csaba.
>
> On Tue, Mar 6, 2018 at 2:52 AM, Paul Anderson wrote:
>
>> Raghavendra,
>>
>> Thanks very much for your reply.
>>
>> I fixed our data corruption problem by disabling the volume
>> performance.write-behind flag
+Csaba.
On Tue, Mar 6, 2018 at 2:52 AM, Paul Anderson wrote:
> Raghavendra,
>
> Thanks very much for your reply.
>
> I fixed our data corruption problem by disabling the volume
> performance.write-behind flag as you suggested, and simultaneously
> disabling caching in my client side mount comman
Tough to do. Like in my case where you would have to install and use Plex.
On March 5, 2018 4:19:23 PM PST, Amar Tumballi wrote:
>>
>>
>> If anyone would like our test scripts, I can either tar them up and
>> email them or put them in github - either is fine with me. (they rely
>> on current buil
>
>
> If anyone would like our test scripts, I can either tar them up and
> email them or put them in github - either is fine with me. (they rely
> on current builds of docker and docker-compose)
>
>
Sure, sharing the test cases makes it very easy for us to see what would be
the issue. I would reco
Raghavendra,
Thanks very much for your reply.
I fixed our data corruption problem by disabling the volume
performance.write-behind flag as you suggested, and simultaneously
disabling caching in my client side mount command.
In very modest testing, the flock() case appears to me to work well -
be
On Mon, Mar 5, 2018 at 8:21 PM, Paul Anderson wrote:
> Hi,
>
> tl;dr summary of below: flock() works, but what does it take to make
> sync()/fsync() work in a 3 node GFS cluster?
>
> I am under the impression that POSIX flock, POSIX
> fcntl(F_SETLK/F_GETLK,...), and POSIX read/write/sync/fsync ar
Hi,
tl;dr summary of below: flock() works, but what does it take to make
sync()/fsync() work in a 3 node GFS cluster?
I am under the impression that POSIX flock, POSIX
fcntl(F_SETLK/F_GETLK,...), and POSIX read/write/sync/fsync are all
supported in cluster operations, such that in theory, SQLite3
12 matches
Mail list logo