mirror of https://gitee.com/bigwinds/arangodb
remove satelites
This commit is contained in:
parent
52b234574e
commit
5d1263a4fe
|
@ -13,14 +13,6 @@ Synchronous replication only works in in a cluster and is typically used for mis
|
|||
|
||||
Synchronous replication is organized in a way that every shard has a leader and r-1 followers. The number of followers can be controlled using the `replicationFactor` whenever you create a collection, the `replicationFactor` is the total number of copies being kept, that is, it is one plus the number of followers.
|
||||
|
||||
### Satellite collections
|
||||
|
||||
Satellite collections are synchronously replicated collections having a dynamic replicationFactor.
|
||||
They will replicate all data to all database servers allowing the database servers to join data
|
||||
locally instead of doing heavy network operations.
|
||||
|
||||
Satellite collections are an enterprise only feature.
|
||||
|
||||
### Asynchronous replication
|
||||
|
||||
In ArangoDB any write operation will be logged to the write-ahead log. When using Asynchronous replication slaves will connect to a master and apply all the events from the log in the same order locally. After that, they will have the same state of data as the master database.
|
||||
|
|
|
@ -140,12 +140,6 @@ to the [naming conventions](../NamingConventions/README.md).
|
|||
servers holding copies take over, usually without an error being
|
||||
reported.
|
||||
|
||||
When using the *Enterprise* version of ArangoDB the replicationFactor
|
||||
may be set to "satellite" making the collection locally joinable
|
||||
on every database server. This reduces the number of network hops
|
||||
dramatically when using joins in AQL at the costs of reduced write
|
||||
performance on these collections.
|
||||
|
||||
`db._create(collection-name, properties, type)`
|
||||
|
||||
Specifies the optional *type* of the collection, it can either be *document*
|
||||
|
|
|
@ -73,12 +73,6 @@ If set to *true*, then the additional query profiling information will be return
|
|||
in the sub-attribute *profile* of the *extra* return attribute if the query result
|
||||
is not served from the query cache.
|
||||
|
||||
@RESTSTRUCT{satelliteSyncWait,JSF_post_api_cursor_opts,boolean,optional,}
|
||||
This *enterprise* parameter allows to configure how long a DBServer will have time
|
||||
to bring the satellite collections involved in the query into sync.
|
||||
The default value is *60.0* (seconds). When the max time has been reached the query
|
||||
will be stopped.
|
||||
|
||||
@RESTDESCRIPTION
|
||||
The query details include the query string plus optional query options and
|
||||
bind parameters. These values need to be passed in a JSON representation in
|
||||
|
|
Loading…
Reference in New Issue