|
Is there a scheduled downtime for DBpedia, or did I just pick an unfortunate time to ask it about hockey? Both my code and my browser at getting 503's at the moment, where they weren't 10 minutes ago. |
|
:( Too many people uses dbpedia as a sandbox, and some ill queries runs much longer than predicted by the compiler, causing redundand load and wasted working set. Fortunately, many important applications use private replicas of dbpedia (or whole LOD), so they does not suffer from unpredictable overloads of the public server and the public served does not suffer from quite predictable overloads of these apps :) The scheduled downtime of DBpedia is quite minor and the cache warm-up after start is very aggressive, so the lag between server start and reaching 30-50% of the peak performance is surprisingly small. Scheduled downtimes of LOD are a bit longer (at least I've seen maintainance page on LOD myself but I've never seen it on dbpedia). The long part of LOD maintainance is free-text indexing, because both the number of graphs and the size of vocabulary are "a bit bigger" than average. dbpedia is more convenient for free-text because it's all about single graph. Would you say, then, that the 503 response I saw (which was also matched by the dbpedia.org site) today was due to a scheduled downtime? I noticed the site and endpoint were back up within the hour. The DBpedia SPARQL endpoint was down for a scheduled binary upgrade today, as announced on twitter ... @Jerven: OpenLink's twitter account, perhaps: http://twitter.com/OpenLink or maybe search for hashtag #dbpedia. HTH |
|
According to Mondeca's SPARQL Endpoint Status, DBpedia has a service disruption right now (it's red). Don't know if it's scheduled. Serves me right for not giving the Endpoint Status site more than a few minutes to detect the outage. At least I know it isn't just me now :) |
