llamerada-jp/colonio

Library let it easy to use distributed systems

colonio's Issues

bug: should return error when send message to exited node

• golang
• create cluster with more than 3 nodes
• down a node
• send message to the node that is downed

Decent error handling in go lang

add delete method for kvs

only support binary array as value instead of Value class

• remove value class
• use std::shared_ptr<std::vector<uint8_t>> or make custom container to deal binary efficientry

scheduler may have a bug

https://github.com/llamerada-jp/colonio/actions/runs/5035597963/jobs/9031296743

[ RUN      ] SchedulerNativeTest.add_and_remove
wait_signal(end)
pass_signal(end)
/Users/runner/work/colonio/colonio/test/core/scheduler_native_test.cpp:68: Failure
Expected equality of these values:
  "12"
  helper.get_route().c_str()
    Which is: "1"
[  FAILED  ] SchedulerNativeTest.add_and_remove (0 ms)

'authenticate' and 'poll' are called after disconnect

Could not reproduce this bug in local Linux(WSL2) env. It may only be for macOS env.
https://github.com/llamerada-jp/colonio/actions/runs/5025082933/jobs/9013202506#step:4:1984

Patch feature for KVS

The patch feature is helpful to deal with structured data effectively (like JSON or YAML) in KVS.
I don't want the patch features to depend on the type of structured data. I guess Rocksdb's MergeOperator interface is a good hint to resolve this idea.

Provide local storage interface instead of kvs_get_local_data

Problems to resolve:

• kvs_get_local_data is not efficient. The user program cannot seek locally stored data effectively.
• All data are stored in memory and use a lot of memory when dealing with large data. It looks good to provide the interface to implement a custom module to store local data. So developers can implement the module suitable for each situation.

Abstraction of interfaces related to coordinates

X, Y coordinates, longitude, and latitude are similar, but the order of the arguments is different and can be mistaken. In addition, latitude and longitude may be specified in radian, and degree, so an interface is needed to use them without mistakes.

update routing implement to be more effective

• 'force routing' looks more called than expected
  https://github.com/llamerada-jp/colonio/actions/runs/5025082933/jobs/9013202506#step:4:1984

SetPosition method could not detect errors

if resp is an error instance, Get("x") returns an undefined value and fails to call Float().
https://github.com/llamerada-jp/colonio/blob/main/go/colonio/colonio_wasm.go#L236
do an error check before getting the result values.

Provide lease & optimistic exclusion feature for kvs.

Problems to resolve:
Colonio does not have a lock feature. Clearly, this feature is important for handling data without discrepancies. In colonio, It assumes that nodes are unstable and cannot accurately manage members. In this situation, implementing mutex is very difficult. I considered lease & optimistic exclusion a realistic solution to provide a lock feature.