Client does not respect long running operations about hazelcast-csharp-client

[pveentjer]

Once the operation starts executing; it will not stop. So there are checks in place before starting an operation. but once these hurdles are taken.... the operation keeps running till it complete.

So there is no mechanism in place that:

• prevent running long running operations (since we don't know how long running these operations are)
• and there is no mechanism that aborts long running operations. Only the executor future.cancel has a mechanism to terminate an existing task.

[pveentjer]

I see 2 problems in the logging:
1: apparently the task isn't removed after the initial completion was done otherwise a later completing result should not be able to find the task to complete.
2: the completion of the task isn't atomic; if the task is completed and it gets completed again, it should not throw an exception. It should just be ignored.. first come first served.

[asimarslan]

fixed by #113