Hello all,
we have encountered the following situation during an overnight load test.
We get the following message repeatedly in the couch logs:
** Reason for termination ==
** {compaction_loop_died,
{timeout,{gen_server,call,[0.117.0,start_compact]}}}
At one time, we are getting it
Heya Jason,
not sure this works if you have two way replication, because then the
server gets the delete and there is nothing to bump.
Best
Jan
--
On 26 Nov 2014, at 15:51 , Jason Smith jason.h.sm...@gmail.com wrote:
Hi, Jan. I'm sure you know this already, but to me, the current solution
On 26 Nov 2014, at 10:47 , Alexander Harm cont...@aharm.de wrote:
Hello Jan,
does CouchDB figure out the delta based on a previous sync or always
comparing the full database? Just to know if there is a difference in the
first online sync after an offline sync (assuming the database is
Hi everyone,
this week’s CouchDB Weekly News is out:
http://blog.couchdb.org/2014/11/27/couchdb-weekly-news-november-27-2014/
Highlights:
- Handling Offline Replication / Synchronisation
- more on the CouchDB 2.0 developer preview
… as well as the regular QA, discussions, “get involved”, job
Hi,
this might sound like a terrible idea to someone who knows CouchDB, and if
that's the case, please just take a minute or two, to explain why,
otherwise, if the idea isn't so crazy after all, I hope I'll get some
solutions to my problem:
I'm thinking of creating a platform based on CouchDB,
Hi Peter
Will the users create their own datastructures too?
If not this sounds like sql on relational tables might be a better tool for
the problem.
It seems to me you're hitting exactly the weak point of most nosql
solutions.
Alex
2014-11-28 0:49 GMT+01:00 Peter Grman peter.gr...@gmail.com:
Hi Alex,
Yes, the users would be able to import different sets of data, which isn't
relational, and use the platform to analyse it. The analysed data would be
in 99% of the cases append only (+ removing old data) and the data can be
defined by the user, as well as be hierarchical.
When I thought
sounds like a very interesting application
seems like you dont care if the user has to wait for an index to be built
when the user creates a query
Alex
2014-11-28 2:23 GMT+01:00 Peter Grman peter.gr...@gmail.com:
Hi Alex,
Yes, the users would be able to import different sets of data, which
sorry for being off-topic
Alex
2014-11-28 2:52 GMT+01:00 Alexander Gabriel a...@barbalex.ch:
sounds like a very interesting application
seems like you dont care if the user has to wait for an index to be built
when the user creates a query
Alex
2014-11-28 2:23 GMT+01:00 Peter Grman
No, I don't. The program should be for analysing logs (collected by
fluentd) - should be open source and on github, however there isn't much
done yet: https://github.com/logTank/
The index rebuilding shouldn't be a problem as CouchDB will be only used
for general stats and the user actually won't
I believe os_process_timeout applies to view servers (default is 5 seconds)
so you can configure the timeout for view queries, not sure about CPU/HDD
Space (although inspecting _stats might shed some light).
Ta.
On 28 November 2014 at 10:12, Peter Grman peter.gr...@gmail.com wrote:
No, I
Hi Peter,
An interesting concept ...
This may sound simplistic, but is it viable for your application to initially
have a process where new queries written are vetted by a human before they are
run ? The advantage of this is two-fold, namely:
i) you'll be able to move on a prove your
12 matches
Mail list logo
