Yamamoto, Hirotaka comments

Results 64 comments of


                                            Yamamoto, Hirotaka

Provide binaries for releases

@kiesel Hi. Is a Docker image of transocks enough for you?

Provide binaries for releases

Alright, thank you.

transocks dead lock when the socks met some issues

> error="file tcp 127.0.0.1:1082->114.245.228.53:57912: fcntl: too many open files" This indicates there are too many open files. transocks might be leaking in some cases?

Use transocks to achieve the p2p live video streaming for remote driverless vehicle surveillance.

transocks only supports TCP. As live video streaming typically uses UDP, I don't think using transocks is appropriate.

Cannot replicate because the master purged required binary logs

I'm afraid this is not a bug in MOCO because we cannot do anything if the primary is recreated. Unless you have a good idea to address this, I'd like...

Cannot replicate because the master purged required binary logs

@shunki-fujita not very sure. I have a question about when this really happens. If a primary pod is going to be recreated with CLONE, I guess another pod should become...

Cannot replicate because the master purged required binary logs

@shunki-fujita Thank you, but my question is different. I don't understand why such a recreated pod can continue to be the primary. Normally, such a Pod should become a new...

Cannot replicate because the master purged required binary logs

I mean, your step 3 in the issue body should trigger a fail over. > To Reproduce > Steps to reproduce the behavior: > ... > 3. Re-create primary pod...

Cannot replicate because the master purged required binary logs

Ah, gotcha. Thank you.

Accurate doesn't create a new namespace after resolving an issue with conflicting namespaces

@zoetrope can your team help with the debug? TIA