-
the KVS does not want to initialize. All the logs show is the connect log generating the following. Where can we go to try and get more detail about the error? The lambda functions do not appear to…
-
Following up #6264, it is not clear that the KVS ensures that all data is below the maximum allowed and that errors propogate correctly / consistently. For example:
```
int flux_kvs_txn_put (flux…
-
### Reproduction steps
When running test MCORE_FS_1_4, we start two Matter devices (Lighting Example and Fabric-Bridge) using the same passcode, and attempt to distinguish them using the discriminato…
-
The `flux-coral2-dws` service currently logs a lot of information about workflows to its journal. However, @bdevcich requested that some k8s `Workflow` info (which can be formatted as JSON) be saved t…
-
Recently a large job put a heavy load on the KVS and the KVS was unable to make progress
```
- ev_invoke_pending ▒
- 75.04% conten…
chu11 updated
1 month ago
-
### Please confirm you have already done the following
- [X] I have searched the repository for related/existing bug reports
- [X] I have all the details the issue requires
### Please answer th…
-
A production flux instance became unresponsive recently because the KVS was incapacitated trying to return the output eventlog for a job. The job had apparently gone haywire and was writing the same l…
-
### RFC Description
Today [`discovery.Healthcheck` _(in `go/vt/discovery` - mainly used by `vtgate`)_](https://github.com/vitessio/vitess/blob/main/go/vt/discovery/healthcheck.go#L272) supports fil…
-
Per comment / idea in #6240
Pro: no need to require user to call before calling `content-checkpoint.put`. If backing store isn't loaded, the content module will know not to call `content.flush`.
…
-
This continues conversation from PR #6217. From @garlick
> After consulting with @kkier a bit on this, we think it may be better to present admins with a choice of
> - ensure flux never runs o…
chu11 updated
2 weeks ago