Fri, Jan 14
Thu, Jan 13
Isn't this mostly supported by https://www.wikidata.org/wiki/Wikidata:Listeria? What are the features missing?
Wed, Jan 12
Tue, Jan 11
Mon, Jan 10
Thu, Jan 6
@Papaul do you know if we have spare SSDs for this host?
Wed, Jan 5
Tue, Dec 21
For the moment, elasticsearch is configured explicitly with the IPv4 address of the host. Internal cluster communication does not rely on DNS but on internal cluster discovery mechanism. nginx listens on IPv6 and proxies all external communication. So having an AAAA DNS entry should not break anything. That being said, we should configure IPv6 properly and do some testing.
Mon, Dec 20
Dec 17 2021
After discussion with @RhinosF1 :
Dec 16 2021
All data has been reloaded as part of the new streaming updater. Please re-open if the issue isn't fixed.
Documentation is good enough for now, it is going to be further improved organically as needed.
Dec 13 2021
From the Search Platform point of view, those logs make sense. We log full queries when they failed. In case of specific issues, those logs are useful to understand user facing problems. So unless those logs are causing an issue on our infrastructure, we think it make sense to keep them.
A few notes from discussion with @Jdrewniak:
Let's drop this at the moment, we'll see what we do when we have a concrete need for Emmanuel to have additional access
Nov 29 2021
The Search Platform team does not see much value in those selenium tests. We have additional integration tests that run more complex tests and those are the one that provide value. It might make more sense to completely kill the selenium tests instead of trying to fix them. Please contact @dcausse or @EBernhardson for more context if needed.
Nov 23 2021
Nov 22 2021
Let's go with a single cluster at least for the start. If we hit any real life issue, we can revisit this solution.