network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 11 months |
| seen | Apr 13 at 12:18 | |
| stats | profile views | 1 |
|
Mar 28 |
awarded | Popular Question |
|
Mar 26 |
asked | MongoDB: move documents before capping |
|
Mar 21 |
awarded | Tumbleweed |
|
Mar 17 |
asked | MongoDB: Aggregation workaround by helper collection |
|
Mar 14 |
asked | MongoDB: group and document size limitation with aggregation and MapReduce |
|
Aug 1 |
accepted | mongodb: replica-set processing reads on the primary |
|
Aug 1 |
accepted | MongoDB: RAM requirements |
|
Aug 1 |
accepted | mongodb: replica-set with load balancer |
|
Jul 2 |
comment |
mongodb: replica-set processing reads on the primary shouldn't the php driver deal with the replicaset correctly and NOT push all read requests to the master/write server?! |
|
Jun 29 |
asked | mongodb: replica-set processing reads on the primary |
|
Jun 28 |
asked | mongodb: drop all collections |
|
Jun 26 |
asked | mongodb: replica-set with load balancer |
|
Jun 21 |
comment |
MongoDB: Replica Set - master vs. slave Trying the master slave replication by editing the config seems to work. But how can it automatically failover the master with the "hard-coded", strictly defined master=true/false in the config file on each mongos? |
|
Jun 21 |
comment |
MongoDB: Replica Set - master vs. slave If i understand this correctly, it is only writing with one of the servers within the replica-set, but i do not have to care which one is the master? mongodb master-slaves do manage and failover or sync themselves, really possible? how inconvenient was mysql... |
|
Jun 20 |
accepted | MongoDB: Replica Set - master vs. slave |
|
Jun 20 |
asked | MongoDB: Replica Set - master vs. slave |
|
Jun 19 |
asked | MongoDB: RAM requirements |
|
Jun 19 |
awarded | Scholar |
|
Jun 19 |
accepted | MongoDB: queue vs. realtime write/update |
|
Jun 18 |
awarded | Student |
