search for: 60s

Displaying 20 results from an estimated 219 matches for "60s".

Did you mean: 60
2011 Dec 08
5
Master repeatedly killing workers due to timeouts
...w problems and I''m at a loss what might cause it. A number of times in the past few days, our unicorn slaves keep timing out & the master keeps restarting them. unicorn.log looks something like : E, [2011-12-08T18:11:32.912237 #26661] ERROR -- : worker=5 PID:15367 timeout (61s > 60s), killing E, [2011-12-08T18:11:32.952041 #26661] ERROR -- : reaped #<Process::Status: pid 15367 SIGKILL (signal 9)> worker=5 I, [2011-12-08T18:11:32.985925 #17824] INFO -- : worker=5 ready E, [2011-12-08T18:11:42.962869 #26661] ERROR -- : worker=3 PID:15499 timeout (61s > 60s), killing E,...
2019 Apr 04
0
Solr connection timeout hardwired to 60s
On 4/4/2019 2:21 AM, Peter Mogensen via dovecot wrote: > What's the recommended way to handling timeouts on large mailboxes given > the hardwired request timeout of 60s in solr-connection.c: > > http_set.request_timeout_msecs = 60*1000; I'm a denizen of the solr-user at lucene.apache.org mailing list. For a typical Solr index, 60 seconds is an eternity. Most people aim for query times of 100 milliseconds or less, and they often achieve that goa...
2019 Apr 13
0
Solr connection timeout hardwired to 60s
...w Dovecot operates towards Solr it will flush > ~1000 documents towards Solr in /update request until it has traversed > the mailbox (let's say 20.000 mails), doing softCommits after each. > > But is it really reasonable for Dovecot to expect that no request will > take more than 60s to process by Solr? > It doesn't seem like my Solr can handle that, although it does process > documents and it does reasonably fast clear pending documents after > Dovecot closes the connection. > > On the surface it looks like Dovecot is too impatient. > > /Peter If this...
2019 Apr 04
4
Solr connection timeout hardwired to 60s
Hi, What's the recommended way to handling timeouts on large mailboxes given the hardwired request timeout of 60s in solr-connection.c: http_set.request_timeout_msecs = 60*1000; /Peter
2019 Apr 12
2
Solr connection timeout hardwired to 60s
...m my understanding of how Dovecot operates towards Solr it will flush ~1000 documents towards Solr in /update request until it has traversed the mailbox (let's say 20.000 mails), doing softCommits after each. But is it really reasonable for Dovecot to expect that no request will take more than 60s to process by Solr? It doesn't seem like my Solr can handle that, although it does process documents and it does reasonably fast clear pending documents after Dovecot closes the connection. On the surface it looks like Dovecot is too impatient. /Peter On 4/10/19 6:25 PM, Peter Mogensen wrote...
2019 Apr 10
0
Solr connection timeout hardwired to 60s
On 4/4/19 6:57 PM, Peter Mogensen wrote: > > > On 4/4/19 6:47 PM, dovecot-request at dovecot.org wrote: >> For a typical Solr index, 60 seconds is an eternity. Most people aim >> for query times of 100 milliseconds or less, and they often achieve >> that goal. > > I'm pretty sure I get these while indexing, not querying. > > Apr 04 16:44:50 host
2011 May 20
0
hang in select() on unix domain sockets, 60s timeout loop
I have rsync 3.0.8 on both ends, over ssh, which on remote server appears to be hung in select(): Process has fd 0, 1, 2, and all are unix sockets it's just hung, keeps timing out every 60 seconds then calls select again it's been hung for 15 hours flags on the remote are: --server --sender -lHogDtpAXrRe.iLs --numeric-ids --inplace it loops every 60 seconds with: select(1,
2018 Oct 25
2
Possible bug in Opus 1.3 (opus-tools-0.2-opus-1.3)?
...w logical stream (#1, serial: 000028fd): type opus Encoded with libopus 1.3, libopusenc 0.2.1 User comments section follows... ENCODER=opusenc from opus-tools 0.2-3-gf5f571b ENCODER_OPTIONS=--bitrate 56 --vbr --comp 5 ALBUM=Test-Sweeps ARTIST=Audacity COMMENT=60s logarithmic sweep (0-20kHz): 5s=10Hz, 10s=20Hz, 15s=39Hz, 20 s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s= 10kHz, 60s=20kHz COMMENTS=60s logarithmisch DATE=2016 TITLE=Sweep (0-20kHz at 96kHz) log TRACKNUMBER=2 Opus stream 1:...
2019 Apr 04
2
Solr connection timeout hardwired to 60s
On 4/4/19 6:47 PM, dovecot-request at dovecot.org wrote: > For a typical Solr index, 60 seconds is an eternity. Most people aim > for query times of 100 milliseconds or less, and they often achieve > that goal. I'm pretty sure I get these while indexing, not querying. Apr 04 16:44:50 host dovecot[114690]: indexer-worker(me at example.com): Error: fts_solr: Indexing failed: Request
2019 Apr 14
0
Solr connection timeout hardwired to 60s
On 14/04/2019 17:16, Peter Mogensen via dovecot wrote: > sorry... I got distracted half way and forgot to put a meaningfull > subject so the archive could figure out the thread. - resending. > > On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: > >>> Solr ships with autoCommit set to 15 seconds and openSearcher set to >>> false on the autoCommit.? The
2018 Nov 02
6
Antw: Re: Possible bug in Opus 1.3 (opus-tools-0.2-opus-1.3)?
...rithmisch sweep. Is that a fixed number of Hertz per second (SoX calls that linear)? Or a fixed number of semitones per second (SoX calls that exponantional)? (The ogg comment says 5s=10Hz, 10s=20Hz, 15s=39Hz, 20s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s=10kHz, 60s=20kHz so it seems the frequency rises logarithmically.) $ sox -c 1 -r 96k -b 16 -n /tmp/sweep.wav synth 60 sin create 1-20 gain -3 > With Opus I noticed that the file size for 48kHz and 48 kbps > compared to 96kHz Vorbis at 31kbps is about double the size Your opusenc line says "--bit...
2019 Apr 05
1
Solr connection timeout hardwired to 60s
> I'm a denizen of the solr-user at lucene.apache.org mailing list. > [...] > Here's a wiki page that I wrote about that topic. This wiki is going > away next month, but for now you can still access it: > > https://wiki.apache.org/solr/SolrPerformanceProblems That's a great resource, Shawn. I am about to put together a test case to provide a comprehensive FTS
2010 Oct 22
4
502 bad gateway on nginx with recv() failed
Hi, I''m serving the puppetmaster application with its config.ru through unicorn - proxied by nginx. I''m using unix sockets, 4 workers, and 2048 backlog. The clients - after their typical "puppet run" - send back a report to the master in YAML. Some clients whose reports tend to be large (close to 2mb) get a 502 bad gateway error and error out. nginx log: 2010/10/22
2015 Oct 18
3
Hibernation disabled when mailbox selected
After setting imap_hibernate_timeout to 60s, I could not find any hibernated connections after a few hours. I tested hibernation and made an observation: IDLE'd imap sessions only hibernate if they don't have a mailbox SELECT'd, otherwise they never hibernate. Is this the way it's supposed to work? Joseph Tam <jtam.home...
2019 Apr 14
2
Solr connection timeout hardwired to 60s
sorry... I got distracted half way and forgot to put a meaningfull subject so the archive could figure out the thread. - resending. On 4/14/19 4:04 PM, dovecot-request at dovecot.org wrote: >> Solr ships with autoCommit set to 15 seconds and openSearcher set to >> false on the autoCommit.? The autoSoftCommit setting is not enabled by >> default, but depending on how the index
2019 Apr 14
0
[PATCH] Re: Solr connection timeout hardwired to 60s
On 13/04/2019 17:16, Shawn Heisey via dovecot wrote: > On 4/13/2019 4:29 AM, John Fawcett via dovecot wrote: >> If this value was made configurable people could set it to what they >> want. However the underlying problem is likely on solr configuration. > > The Jetty that is included in Solr has its idle timeout set to 50 > seconds.? But in practice, I have not seen this
2006 Jun 14
2
AddQueueMember and Local channels
...om a posting yesterday from Kevin, I have the following in the dialplan: exten => 709,1,AddQueueMember(SomeQueue|Local/706@AgentQ) I am on extension 706. From the CLI: SomeQueue has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime), W:0, C:0, A:3, SL:0.0% within 60s No Members No Callers I call 709, get a console message NOTICE[30879]: app_queue.c:3122 aqm_exec: Added interface 'Local/706@AgentQ' to queue 'SomeQueue' from the CLI: SomeQueue has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime), W:0, C...
2018 Nov 01
0
Possible bug in Opus 1.3 (opus-tools-0.2-opus-1.3)?
...rithmisch sweep. Is that a fixed number of Hertz per second (SoX calls that linear)? Or a fixed number of semitones per second (SoX calls that exponantional)? (The ogg comment says 5s=10Hz, 10s=20Hz, 15s=39Hz, 20s=78Hz, 25s=156Hz, 30s=312Hz, 35s=625Hz, 40s=1.25kHz, 45s=2.5kHz, 50s=5kHz, 55s=10kHz, 60s=20kHz so it seems the frequency rises logarithmically.) $ sox -c 1 -r 96k -b 16 -n /tmp/sweep.wav synth 60 sin create 1-20 gain -3 > With Opus I noticed that the file size for 48kHz and 48 kbps > compared to 96kHz Vorbis at 31kbps is about double the size Your opusenc line says "--bit...
2023 Sep 12
0
njs-0.8.1
...a content handler to run at regular interval. The handler receives a session object as its first argument, it also has access to global objects such as ngx. : example.conf: : location @periodics { : # to be run at 1 minute intervals in worker process 0 : js_periodic main.handler interval=60s; : : # to be run at 1 minute intervals in all worker processes : js_periodic main.handler interval=60s worker_affinity=all; : : # to be run at 1 minute intervals in worker processes 1 and 3 : js_periodic main.handler interval=60s worker_affinity=0101; : : resolver 10.0.0.1; : js_f...
2006 Apr 10
1
Call me for testing my system
Dear User, Anybody could dial these sip uri : sip:info@nxs.yi.org (french) sip:music@nxs.yi.org (music 60s) sip:support@nxs.yi.org (french) Thanks for help ___________________________________________________________________________ Nouveau : t?l?phonez moins cher avec Yahoo! Messenger ! D?couvez les tarifs exceptionnels pour appeler la France et l'international. T?l?chargez sur http://...