Hi,
Is it possible with ArangoDB 3 to set up such a cluster environment (i.e.
with automatic failover and rebalancing) without having to rely on mesos?
In other words, how tight is the coupling of ArangoDB 3 and mesos?
The reason I'm asking this is that we are currently considering other
orches
0
> However, a certain amount of work is always needed to do the integration
> with different Cloud orchestrating frameworks.
> In 3.0 automatic failover and rebalancing in the above sense is done
> completely inside of the ArangoDB cluster - as long as you use synchronous
> repl
> unfortunately one of the things we are still missing, but we will
> definitely have this in place for the release.
>
> Am Mittwoch, 25. Mai 2016 22:49:17 UTC+2 schrieb Bart DS:
>>
>> Hi Willi,
>>
>> Thanks for this very detailed explanation.
>> If I unde
ers,
> Max
>
> Am 25. Mai 2016 23:50:12 MESZ, schrieb Bart DS >:
> >Hi Max,
> >
> >This sounds very promising!
> >What's the estimated timeframe for the 3.0 release?
> >
> >Regarding client connections, is the official arangojs client cluster
Hi Max,
On Thursday, May 26, 2016 at 8:15:33 PM UTC+2, Max Neunhöffer wrote:
>
> Hi Bart,
>
> On Thu, May 26, 2016 at 12:01:38AM -0700, Bart DS wrote:
> > Hi Max,
> >
> > That's great!
> > Please let me know when you have more information r
First of all congratulations on the new 3.0 release!
Much improved clustering with auto-failover, Velocypack, persistent
indexes, etc are all great new features.
Unfortunately I'm having several issues getting the new clustering working.
As discussed in an earlier post, I'm interested in setting
r printing 2 warnings regarding "higher
term than RPC caller"
Bart
> Am Sonntag, 26. Juni 2016 18:36:46 UTC+2 schrieb Bart DS:
>>
>> First of all congratulations on the new 3.0 release!
>> Much improved clustering with auto-failover, Velocypack, persistent
>&
Hi Kaveh,
On Monday, June 27, 2016 at 9:07:40 AM UTC+2, Kaveh Vahedipour wrote:
>
> Hello Bart,
>
> Could you please provide us with some details like OS and docker versions
> your are running. The startup process like rough timings and such. In short
> I'd be extremely grateful with any kind o
try to create a fix asap.
>
> Best
> Frank
>
> Am Montag, 27. Juni 2016 09:32:04 UTC+2 schrieb Bart DS:
>>
>> Hi Kaveh,
>>
>>
>> On Monday, June 27, 2016 at 9:07:40 AM UTC+2, Kaveh Vahedipour wrote:
>>>
>>> Hello Bart,
>>>
Hi Kaveh,
I tried building it myself using your instructions, but the build fails
with an error regarding regex support:
bart@laptop ~/arangodb/build $ cmake ..
-- The CXX compiler identification is GNU 4.8.5
-- The C compiler identification is GNU 4.8.5
-- The ASM compiler identification is GNU
eed at least GCC 4.9 in order to build ArangoDB 3.0
> > It was the first version to bring stable support for C++11 Regex.
> >
> > Cheers,
> > Willi
> >
> > On Monday, June 27, 2016 at 5:46:01 PM UTC+2, Bart DS wrote:
> > Hi Kaveh,
> >
&
Ok, I did some tests and the agents are running fine now.
At least, initially...
When I start my first server via the following command:
./build/bin/arangod --server.authentication=false --server.endpoint
tcp://0.0.0.0:8529
--cluster.my-address tcp://127.0.0.1:8529 --cluster.my-local-info db1
threaded cores you have available. I
> generally build with make -j8 for example.
>
> Anyway, many thanks for hanging in there. Contributions like yours advance
> the development considerably.
>
> Keep us posted, please.
>
> Kind regards,
> Kaveh.
>
> > On 28 Jun
Doh, I should have tried that before reporting back...
Anyway, I removed the old databases and restarted everything (3 agents, 2
DBServers and 1 coordinator)
Several minutes after starting the coordinator (a lot of messages appear
regarding synchronization of shards) everything seems to run and
;
> cd arangodb
> ./scripts/startLocalCluster 3 2 1
>
> The log and databases end up in cluster. Could you please share those logs
> with me?
>
> Kind regards,
> Kaveh
>
>
> > On 28 Jun 2016, at 14:08, Bart DS >
> wrote:
> >
> > Doh, I should have
Ok, so if I understand correctly I shouldn't worry about the missing data
in the web interface for now as a fix for it will be available in 3.0.1?
Is that correct?
regards,
Bart
On Tuesday, June 28, 2016 at 4:03:14 PM UTC+2, Kaveh Vahedipour wrote:
>
> Hi Bart,
>
> > With this script, the clu
On Tuesday, June 28, 2016 at 4:15:02 PM UTC+2, Kaveh Vahedipour wrote:
>
> yes, exactly.
>
> cheers,
> kaveh
>
>
Ok, that's great!
And thank you very much for the great support, I really appreciate that!
regards,
Bart
--
You received this message because you are subscribed to the Google G
Hi,
What is the recommended / most performant way to keep track of read status
of message conversations in a multimodel database such as ArangoDB?
To give an example:
There are 4 users logged in in the system: A, B, C and D
Users A, C and D are starting a chat session and start sending messages
Hi,
I can't restore a database dump over SSL:
arangorestore --server.endpoint ssl://localhost:8530
--server.authentication true --server.username root
--include-system-collections false --server.database testdb
--create-database false --input-directory ./arangodump_2017-03-08
Please specify a
god in your start
> script or arangod's configuration file?
>
> Can you also post on which platform you run it on plus the output of
> `arangorestore --version`. This will show some library version numbers.
> Thanks!
> Jan
>
>
> Am Donnerstag, 9. März 2017 09:43:0
9T10:52:31Z [3517] ERROR {communication} unable to perform ssl
handshake: wrong version number : 336109835
Thanks.
Bart
On Thursday, March 9, 2017 at 12:22:48 PM UTC+1, Bart DS wrote:
>
> Hi Jan,
>
> Apparently the issue was caused by the default SSL protocol used by
> arangores
ost:8530
> --server.authentication true --server.username root
> --include-system-collections false --server.database testdb
> --create-database false --input-directory ./arangodump_2017-03-08
> --ssl.protocol 5
>
> Thanks
> Jan
>
>
> Am Donnerstag, 9. März 2017 12:
ished.
> I am confused, because the two port numbers should match. Has the above
> output been edited so it shows a wrong port number?
> Can you double-check that you are using --ssl.protocol 5 on the correct
> port when using the SSH tunnel?
>
> Thanks
> Jan
>
> 2017-03-0
; Best regards
> Jan
>
> Am Donnerstag, 9. März 2017 13:24:17 UTC+1 schrieb Bart DS:
>>
>> Hi Jan,
>>
>> My bad, I used the wrong port on the local server.
>> With the correct port number it does work locally.
>>
>> Via the SSH tunnel I st
Hy Frank,
I'm sorry to reply to an old thread, but I'm also regularly seeing the SSL
error "{communication} unable to perform ssl handshake: Connection reset by
peer : 104".
Did you find a cause/solution for this error?
Another SSL related error that regularly appears is: "{communication}
una
25 matches
Mail list logo
