| Time |
Nick |
Message |
| 07:11 |
|
kworstell-isl joined #evergreen |
| 07:22 |
|
kworstell-isl joined #evergreen |
| 07:39 |
|
BDorsey joined #evergreen |
| 08:31 |
|
Dyrcona joined #evergreen |
| 08:36 |
|
rfrasur joined #evergreen |
| 08:49 |
|
jvwoolf joined #evergreen |
| 08:54 |
|
dguarrac joined #evergreen |
| 08:56 |
|
mantis1 joined #evergreen |
| 10:01 |
|
mmorgan joined #evergreen |
| 10:10 |
Dyrcona |
This JabberClient instance is no longer connected to the server |
| 10:13 |
Dyrcona |
ejabberd.log is, of course, useless. |
| 10:26 |
miker |
Dyrcona: I have ideas for making facets always faster (or at least never slower) since they can be turned into unique int IDs, but tuits... |
| 10:29 |
Dyrcona |
miker: Sounds cool. I also think that should be a separate bug from the ones I'm testing. It's just something that I've noticed. |
| 10:30 |
Dyrcona |
It's not always slower, just sometimes. |
| 10:30 |
* Dyrcona |
goes fishing through logs for a really crazy search to test. |
| 10:45 |
Dyrcona |
So, that jabber thing that I reported earlier: Has anyone ever seen services crash and have 8 listeners all using 100% cpu? This appears to have happened right after I restarted services this morning. |
| 10:47 |
Dyrcona |
I suspect something in the configuration must be busted. |
| 10:57 |
Dyrcona |
Huh. Just restarting ejabberd seems to have fixed it for now. |
| 11:06 |
|
Christineb joined #evergreen |
| 11:06 |
|
kworstell_isl joined #evergreen |
| 11:39 |
* Dyrcona |
signs off on a couple of security branches. |
| 11:55 |
mmorgan |
Dyrcona++ |
| 11:56 |
Dyrcona |
miker++ # For the fixes. |
| 12:40 |
jvwoolf |
Question for sys admins. We're planning a full reingest after our 3.9 upgrade, for symspell and for some indexing changes we wanted to make not related to the upgrade. Now that parallel reingesting with symspell doesn't require the database triggers to be disabled, would y'all still recommend keeping Evergreen offline for such a reingest? Or would it be OK to have it running? |
| 12:41 |
jvwoolf |
(We don't have symspell in our current version, still on 3.6.5) |
| 12:49 |
pinesol |
News from commits: Docs: updating Global Flags docs <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=8326611f8dc232dda993dca412e429713189999a> |
| 13:49 |
csharp_ |
jvwoolf: it's definitely quicker without all the triggers if you can spare the downtime |
| 13:54 |
jvwoolf |
csharp_++ |
| 13:55 |
jvwoolf |
We have some time so I might test still test with triggers and without |
| 13:56 |
jvwoolf |
My guess is that the libraries may prefer to be offline than to have their Sunday staff let loose on a new version that might be slow because of the reingest, but I'll ask that question to our user group |
| 14:05 |
Dyrcona |
I think there are some patches in working branches that can make the ingest more palatable, but it looks like I have it on my other laptop, unless the one I was looking at went in. |
| 14:07 |
jvwoolf |
Dyrcona: The fix for bug 1931737 is in 3.9.1 |
| 14:07 |
pinesol |
Launchpad bug 1931737 in Evergreen 3.8 "Did you mean breaks parallel reingest and causes deadlocks when loading/overlaying bib records in the client" [High,Fix committed] https://launchpad.net/bugs/1931737 |
| 14:08 |
jvwoolf |
Running a reingest with the --delay_symspell flag enabled now |
| 14:08 |
Dyrcona |
yeah, I think that's the one that I was thinking of . |
| 15:51 |
|
jvwoolf left #evergreen |
| 17:06 |
|
mmorgan left #evergreen |
