sinpo828 comments

Results 10 comments of


                                            sinpo828

pulsar-client-go appears to report message too large before compressing it.

any updates on this issue? We meet the same problem recently.

pulsar-client-go appears to report message too large before compressing it.

> This issue is now becoming a problem for us in Go pulsar functions again, due to occasional large JSON messages which would likely compress very well, only they appear...

[issue 447] double check message size when client enable compress

> Hello, I think this problem may be resolved in #805 . https://github.com/apache/pulsar-client-go/pull/805/files#diff-8adb09af2175be5751840343e14df2220a2154ca4bc8de21157ed112be25b6b9L521-L533 > > Hi @Gleiphir2769, according to the implement of Java-Client, it should also check 'encryptedPayload' not only...

runtime: cgo stuck because of go signal handler went into dead loop

[@ianlancetaylor](https://github.com/ianlancetaylor) can you help me, thanks very much.

runtime: cgo stuck because of go signal handler went into dead loop

@tarikkilic GCC does not support `-fsanitize=memory`. Try use clang instead.

runtime: cgo stuck because of go signal handler went into dead loop

Yep. The issue occurs on product enviroment. We are trying recompile the docker images but it may take several days to update all services nodes and reproduce(if not fixed) the...

runtime: cgo stuck because of go signal handler went into dead loop

> @cocktail828 can you confirm if the issue is still happening after recompiling? Sorry for late response. It does not happened for now. I will keep trace the issue. If...

runtime: cgo stuck because of go signal handler went into dead loop

@joedian Sorry to interrupt you. The issue reproduce again(go 1.19) after big traffic. I have update this issue with the latest info.

runtime: cgo stuck because of go signal handler went into dead loop

I will try to simplify the reproduction conditions. But before that, I have no short way.

[RFC]: [Mooncake - Master] Persistence and Recovery Solution for KV Metadata and Segment Information

@ykwd Could you please review this RFC?