kwisatz commented on issue #3488:
URL: https://github.com/apache/jena/issues/3488#issuecomment-5084113753
They're identical machines in terms of specs with both 8Gb of memory and 2Gb
of Swap (Preprod/Production).
Pressure on memory is minimal on both systems with 1.3-1.7Gb used and ~5Gb
in buff/cache.
The preprod machine could of course have received fewer requests, but until
recently, changes were `PUT` every hour with both machines receiving about the
same volume of data.
```json
{
"count" : 317703 ,
"tripleCount" : 317703 ,
"quadCount" : 0
}
```
There's one thing I've seen on the production machine when I grepped the
logs for `Transaction`, but which hasn't happened since July 20th (and with the
problem still ocurring on July 23rd, it may not even be related). The timestamp
coincides with a `PUT` to one of the databases on the system.
```
Jul 20 07:30:05 jena-p fuseki-server[813769]: 07:30:05 WARN Fuseki
:: [202180] Transaction still active - no commit or abort seen (forced abort)
Jul 20 08:30:05 jena-p fuseki-server[813769]: 08:30:05 WARN Fuseki
:: [209460] Transaction still active - no commit or abort seen (forced abort)
Jul 20 09:30:05 jena-p fuseki-server[813769]: 09:30:05 WARN Fuseki
:: [218227] Transaction still active - no commit or abort seen (forced abort)
```
This entry does not occur on the preprod server (`jena-t`), despite the same
2 databases being put at the same interval.
--
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]
