> On 24. Nov 2017, at 06:53, Johs Ensby wrote:
>
> Hi,
> could someone give me the top three benefits of using single node 2.1.1 over
> 1.7.1 and vice versa?
2.1.1 > 1.7.1:
- multicore view/mango indexing, even on single nodes vie sharding
- significantly faster compaction and less i/o-hungry
Hi Mike,
this is a great proposal, thanks a lot! I like this general idea, I guess this
was what Adam was hinting at in the _access draft review ;)
I left one comments inline.
> On 22. Nov 2017, at 14:56, Mike Rhodes wrote:
>
> All,
>
> Just to be clear before starting: this is a proposal fr
I’m +1 as well.
Not to derail this particular discussion (but watch me do it anyway ;):
it be great if we could add a metric akin to “slow queries” that gets
incremented every time we do the fallback. Ideally then this could be
shown in Fauxton is growing steadily, and external monitoring can look
Johs,
Good question. I think really it comes down to allowing the developer more
options in how they access data, and how the database can help this be more
efficient.
I don't think it reduces the usefulness of clustering. We still have three
replicas of each shard, which allows different node
