Coolio, so how long should I wait for that status message to change
locally before I start fretting? It's been the same for like a good 10
minutes, though I'm pushing to a remote couchy host on the
intarwebs
(FYI, my local database is 7.1MB compacted, has 756 docs and is at seq# 1318)
On Tue
Awesome - will make sure I Pull ;)
Thanks,
Nick
On Wed, Nov 4, 2009 at 2:04 PM, Adam Kocoloski wrote:
> Hi Nick, pulling attachments should be much better. It's able to use the
> standalone attachment API and thus avoid the Base64 encoding overhead of the
> push approach. The data is streame
Hi Nick, pulling attachments should be much better. It's able to use
the standalone attachment API and thus avoid the Base64 encoding
overhead of the push approach. The data is streamed directly to the
DB file, so the whole attachment never needs to fit in memory. Best,
Adam
On Nov 3, 2
What about pulling attachments?
I'm getting real close to shoving attachments into my docs and would like to
be able to replicate the docs with attachments
Nick
On Wed, Nov 4, 2009 at 12:47 PM, Adam Kocoloski wrote:
> Thanks Matt & Matt, we should put a big warning sticker on the replicato
Howdy,
I've been watching a push replication in Futon that's been crunching
for a while with the following message:
"W Processed source update #176"
Does this mean that the remote server has process my local revisions
up to sequence number 176? Also, should I be able to see an active
task, or som
Yeah, that's too long, something seems to have gone south. If
possible I'd try restarting CouchDB and then the replication. Best,
Adam
On Nov 3, 2009, at 3:37 PM, Zachary Zolton wrote:
Coolio, so how long should I wait for that status message to change
locally before I start fretting? It's
On Nov 3, 2009, at 3:23 PM, Zachary Zolton wrote:
Howdy,
I've been watching a push replication in Futon that's been crunching
for a while with the following message:
"W Processed source update #176"
Does this mean that the remote server has process my local revisions
up to sequence number 176?
I also experienced the same problems with replication + attachments.
- Matt
On Tue, Nov 3, 2009 at 4:51 PM, Matt Goodall wrote:
> 2009/11/3 Adam Kocoloski :
> > Yeah, that's too long, something seems to have gone south. If possible
> I'd
> > try restarting CouchDB and then the replication. Be
Thanks Matt & Matt, we should put a big warning sticker on the
replicator saying "don't push attachments" :( Getting push
replication to efficiently handle attachments is a blocker for the
next release as far as I'm concerned. Best,
Adam
On Nov 3, 2009, at 7:58 PM, Matt Aimonetti wrote:
2009/11/3 Adam Kocoloski :
> Yeah, that's too long, something seems to have gone south. If possible I'd
> try restarting CouchDB and then the replication. Best,
I've also been experiencing similar problems with replication hanging
recently so I set about reproducing it tonight.
In the end it wa
10 matches
Mail list logo
