I agree and think that at least a mailing post here and on wikidata-tech would've been great to make sure everyone has the chance to know what's going on. For example, I like the way status updates are posted on labs-l for updates on the labs cluster.
Best regards Bene
Am 03.02.2016 um 21:44 schrieb Andra Waagmeester:
Nice that the SPARQL service is upgraded. We noticed something was going on and terminated our bots to wait for more stability.
- Is that stability now reached?
- Is there some sort of flag-mechanism, that would indicate if the
SPARQL endpoint is stable, being upgraded or had change in state?
The SPARQL endpoint is core to our efforts in genewiki's ProteinBoxBot, for a spectrum of reasons. (e.g. concept resolution, identifying data inconsistencies (an item on a gene and protein being incorrectly merged), getting precision and recall numbers on included data sources, etc) Whenever there is an issue, we usually take a step back and retry later. However, this is based on trial and error. It would be quite convenient if we could use a flag-mechanism to decide if we can start or if already started we need to terminate.
Can we do this? Advise on different approaches would be also appreciated.
Regards,
Andra Waagmeester
On Wed, Feb 3, 2016 at 7:53 PM, Stas Malyshev <smalyshev@wikimedia.org mailto:smalyshev@wikimedia.org> wrote:
Hi! > is it me or is the SPARQL service very slow right now? I've upgraded it yesterday to Blazegraph 2.0 and it looks like there was some glitch there. I've restarted it and now it seems to be fine. I'll be watching it and see if it repeats. -- Stas Malyshev smalyshev@wikimedia.org <mailto:smalyshev@wikimedia.org> _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata