Displaying 5 results from an estimated 5 matches for "powool".
2018 Mar 06
1
SQLite3 on 3 node cluster FS?
On Tue, Mar 6, 2018 at 10:58 PM, Raghavendra Gowdappa <rgowdapp at redhat.com>
wrote:
>
>
> On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson <pha at umich.edu> 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, I'll reply inline below...
>>
>> On Mon, Mar 5, 2018 at 10:39 PM, Raghavendra Gowdap...
2018 Mar 06
2
SQLite3 on 3 node cluster FS?
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, Raghavendra Gowdappa
<rgowdapp at redhat.com> wrote:
> +Csaba...
2018 Mar 06
0
SQLite3 on 3 node cluster FS?
On Tue, Mar 6, 2018 at 10:22 PM, Paul Anderson <pha at umich.edu> 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, I'll reply inline below...
>
> On Mon, Mar 5, 2018 at 10:39 PM, Raghavendra Gowdappa
> <rgowdapp at...
2018 Mar 06
0
SQLite3 on 3 node cluster FS?
+Csaba.
On Tue, Mar 6, 2018 at 2:52 AM, Paul Anderson <pha at umich.edu> 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 command.
>
Good to know it worked. Can you give us the
2018 Mar 05
6
SQLite3 on 3 node cluster FS?
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 -
before it would corrupt the db within a few transactions.
Testing using built in sqlite3 locks is