Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote interface: Change into non-blocked RPC #161

Closed
ajblane opened this issue Jun 5, 2019 · 1 comment · Fixed by #162
Closed

Remote interface: Change into non-blocked RPC #161

ajblane opened this issue Jun 5, 2019 · 1 comment · Fixed by #162
Assignees

Comments

@ajblane
Copy link
Collaborator

ajblane commented Jun 5, 2019

In the case of all remote workers which are not workable, blocked PRCs not get RPC results until remote workers are workable. Therefore, remote interface needs to change blocked RPC to non-blocked RPC with 10s. When time-out occurs, remote interface goes to run local dcurl.

@ajblane ajblane self-assigned this Jun 5, 2019
@wusyong wusyong modified the milestone: Centaury Jun 5, 2019
ajblane added a commit to ajblane/dcurl that referenced this issue Jun 5, 2019
In the case of all remote workers which are not workable, blocked PRCs
not get RPC results until remote workers are workable. Therefore,
remote interface needs to change blocked RPC to non-blocked RPC with
10s. When time-out occurs, remote interface goes to run local dcurl.

Pass test with a broker and remote interface without remote worker.

Close DLTcollab#161
@ajblane
Copy link
Collaborator Author

ajblane commented Jun 5, 2019

Here is the test result with a broker and remote interface without remote workers:

$ make BUILD_REMOTE=1 BUILD_DEBUG=1 check
  CC	build/curl.o
  CC	build/constants.o
  CC	build/trinary.o
  CC	build/dcurl.o
  CC	build/implcontext.o
  CC	build/common.o
  CC	build/pow_avx.o
  CC	build/remote_common.o
  CC	build/remote_interface.o
  CC	build/test-trinary.o
  LD	build/test-trinary
*** Validating build/test-trinary ***
	[ Verified ]
  CC	build/test-curl.o
  LD	build/test-curl
*** Validating build/test-curl ***
	[ Verified ]
  CC	build/test-dcurl.o
  LD	build/test-dcurl
*** Validating build/test-dcurl ***
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-RrL7AtIgsQLUmtCaF17O0A 
[dcurl-remote] RPC timeout: request timed out
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-usfeFto5n3HQMjzRtZ0xTw 
[dcurl-remote] RPC timeout: request timed out
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-GSMrICcOF1ss1aJ8APQmBg 
[dcurl-remote] RPC timeout: request timed out
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-TXzscJvYGMsgqgiEFdCMXA 
[dcurl-remote] RPC timeout: request timed out
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-flRh-XTwRpSL20JitnR0zg 
[dcurl-remote] RPC timeout: request timed out
	[ Verified ]
  CC	build/test-pow.o
  LD	build/test-pow
*** Validating build/test-pow ***
CPU - AVX
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
PoW execution times: 1 times.
Success.
	[ Verified ]
  CC	build/test-multi-pow.o
  LD	build/test-multi-pow
*** Validating build/test-multi-pow ***
[dcurl] Implementation CPU (Intel AVX) is initialized successfully
[dcurl-remote] Implementation Remote interface is initialized successfully
[dcurl-remote] callback queue amq.gen-YBfLwcPOjszYHRvpZOi10g 
[dcurl-remote] callback queue amq.gen-8y4UXUNf7ZurixWmRqgCcw 
[dcurl-remote] callback queue amq.gen-mkEJkSdXzKhxRh0DGA5nHw 
[dcurl-remote] callback queue amq.gen-WrcOwOyZhSBgd5m-KVWRjQ 
[dcurl-remote] callback queue amq.gen-TYPyUdhlMI-Afh28bU9NGw 
[dcurl-remote] callback queue amq.gen-yENjMxB10Xb9ZnaPz9cH-w 
[dcurl-remote] callback queue amq.gen-SATKIdxO0lA3K3jZLJ9yDA 
[dcurl-remote] callback queue amq.gen-IIhzNlK2LNPy6Q1KqrQVQw 
[dcurl-remote] callback queue amq.gen-OAl9Bz4juXvPb9R3AZG7Rg 
[dcurl-remote] callback queue amq.gen-Fjt7TM07-PW7fLQcxU-E2w 
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
[dcurl-remote] RPC timeout: request timed out
	[ Verified ]
rm build/test-trinary.o build/test-curl.o build/test-pow.o build/test-multi-pow.o build/test-dcurl.o

ajblane added a commit to ajblane/dcurl that referenced this issue Jun 5, 2019
In the case of all remote workers which are not workable, blocked PRCs
not get RPC results until remote workers are workable. Therefore,
remote interface needs to change blocked RPC to non-blocked RPC with
10s. When time-out occurs, remote interface goes to run local dcurl.

Pass test with a broker and remote interface without remote worker.

Close DLTcollab#161
marktwtn pushed a commit to marktwtn/dcurl that referenced this issue Jun 6, 2019
In the case of all remote workers which are not workable, blocked PRCs
not get RPC results until remote workers are workable. Therefore,
remote interface needs to change blocked RPC to non-blocked RPC with
10s. When time-out occurs, remote interface goes to run local dcurl.

Pass test with a broker and remote interface without remote worker.

Close DLTcollab#161
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants