Takashi Menjo
Takashi Menjo
@mitake ok, i'll try it.
Version 1.0_69_gbf5a0ed also reproduce this.
I cannot reproduce this issue on Sheepdog 0.9.0_244_gff8590b, ZooKeeper 3.4.8 and Ubuntu 16.04. Sheepdog 1.0_65_gb6d64b2, neither.
No. This is not reproduced on fixed-vnodes cluster. As you mentioned, this seems auto-vnode specific problem. I agree that auto-vnode feature should be removed. At least, auto-vnode should be calculated...
The printf format specifier `%d` is not for `size_t` but for (signed) `int`, so your `printf` call may not output a proper value of `mem->mr_size`. How about using `%zu` instead...
Or, how about setting PMEM_LOG_LEVEL for dumping debug log? Please see the "DEBUGGING AND ERROR HANDLING" section in the libpmem man page. https://pmem.io/pmdk/manpages/linux/master/libpmem/libpmem.7/
@yhl25 Here are my specs and their diff. ### For Golang dataplane: ```yaml apiVersion: numaflow.numaproj.io/v1alpha1 kind: Pipeline metadata: name: dci-poc-step2 spec: vertices: - name: in containerTemplate: env: - name: NUMAFLOW_RUNTIME...