Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
7.6.0
-
None
-
Untriaged
-
0
-
No
Description
On Trinity sync'd as of today I run cluster_run and see goxdcr restarting. It happens with a simple:
- ./cluster_run -n 1 --dont-rename
But to get a cbcollect I configure the node with
- ./cluster_connect -n 1 -s 1024 -I 512 -M plasma -T n0:kv+index+n1ql
and have gathered https://s3.amazonaws.com/cb-engineering/stevewatanabe/xdcrRestarts01December2023/collectinfo-2023-12-01T191256-n_0%40cb.local.zip
Summary: Js-evaluator introduced a regression at 1879 due to MB-59925 that is causing goxdcr to exit as soon as it starts the resolver svc
Version bisection:
| Version | Goxdcr crashes? |
|---|---|
| 7.6.0-1776 | No |
| 7.6.0-1845 | No |
| 7.6.0-1878 | No |
| 7.6.0-1879 | Yes |
| 7.6.0-1882 | Yes |
