plvsadi commented on issue #3837:
URL: https://github.com/apache/jena/issues/3837#issuecomment-4195434148

   Hi @afs  Yes the dataset is TDB2. I have managed to do it with a base test 
levels of triples. Few 100s i think. As for the storm, I had somethign runnign 
last night that crashed adn then this morning i started to face this issue. 
Upon investigation came across the bug. So The server at least had 4-5 hours 
after the initial error  to recover.  YOu should be able to use this script
   
   
[fuseki_federation_cancel_wedge_repro.sh](https://github.com/user-attachments/files/26521985/fuseki_federation_cancel_wedge_repro.sh)
   
    This repro script is standalone and public-safe:
   
     How to use it:
     - run it against a Fuseki instance with admin API enabled
     - it creates two temporary TDB2 datasets, loads synthetic triples, runs 
the stress case, and
     then probes the target dataset again
     - it deletes the temp datasets on exit unless `--keep-datasets` is set
   
     Typical same-host usage:
     ```bash
     ./fuseki_federation_cancel_wedge_repro.sh \
       --base-url http://127.0.0.1:3030 \
       --service-base-url http://127.0.0.1:3030 \
       --admin-user admin \
       --admin-password admin
   
     If Fuseki is in Docker and exposed on a host port:
   
     - --base-url should be the host-reachable URL
     - --service-base-url should be the URL that Fuseki itself will use inside 
the SERVICE clause
     - for same-store self-federation that is often still http://127.0.0.1:3030
   
     Expected failure signature:
   
     1. direct probe before stress succeeds
     2. federated probe before stress succeeds
     3. canceled federated-query stress runs
     4. direct probe after stress times out or fails
     5. federated probe after stress also fails or times out
     6. Fuseki restart is needed to recover
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to