As the job is no longer running on the grid (nor using the JVM, for that matter), I guess this is now resolved.

Migrated the grid cronjobs to the new kubernetes jobs.

What about tying the higher limit to a validation that the URL payload is indeed a SPARQL query? If you're really worried about abuse, you could even strip all comments and validate that the remainder is a syntactically valid SPARQL query. That would solve the main pain point of not being able to share long queries, yet not open up a pastebin for arbitrary large amounts of text.

Thanks!

I have reduced the number of CPUs requested to 1, and everything is working again now.

For what it's worth, the $HOME/.lightttpd.conf works as expected when the environment variables TEG_BACKEND_SERVICE_HOST and TEG_BACKEND_SERVICE_PORT are set. Up to now, these were set automatically from the backend deployment, so it's not a separate issue, but indeed caused by the backend failure.

First, quite minimalistic demo is deployed. Tracking further progress on Github.

Deployed an initial demo version. Future progress is tracked in the Github repository.

Another example, currently has 101 results:

Merged and deployed.

Taking this. Tracking progress in Github issue #123.