[jira] [Commented] (RATIS-168) Update Grpc version in Ratis.

2017-12-17 Thread Tsz Wo Nicholas Sze (JIRA)

[ 
https://issues.apache.org/jira/browse/RATIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294480#comment-16294480
 ] 

Tsz Wo Nicholas Sze commented on RATIS-168:
---

There are more relocations than before.  Let me try to understand them.

> Update Grpc version in Ratis.
> -
>
> Key: RATIS-168
> URL: https://issues.apache.org/jira/browse/RATIS-168
> Project: Ratis
>  Issue Type: Bug
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: RATIS-168.001.patch, RATIS-168.002.patch, 
> RATIS-168.003.patch
>
>
> Ratis is using grpc version 1.0.1, This version should be updated to a later 
> version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (RATIS-154) Add setter functions for Raft Config keys

2017-12-17 Thread Tsz Wo Nicholas Sze (JIRA)

 [ 
https://issues.apache.org/jira/browse/RATIS-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze resolved RATIS-154.
---
   Resolution: Fixed
Fix Version/s: 0.2.0-alpha

I have committed this.  Thanks, Shash!

Thanks also Lokesh for reviewing the patch.


> Add setter functions for Raft Config keys
> -
>
> Key: RATIS-154
> URL: https://issues.apache.org/jira/browse/RATIS-154
> Project: Ratis
>  Issue Type: Bug
>Reporter: Mukul Kumar Singh
>Assignee: Shashikant Banerjee
> Fix For: 0.2.0-alpha
>
> Attachments: RATIS-154.001.patch, RATIS-154.002.patch, 
> RATIS-154.003.patch
>
>
> Setter functions are not currently present for all the Raft config keys. The 
> following keys were found to have no setter functions for config keys.
> {code}
> properties.setInt("raft.server.log.segment.cache.num.max", 2);
> properties.setInt("raft.grpc.message.size.max",
> scmChunkSize + raftSegmentSize);
> properties.setInt("raft.server.rpc.timeout.min", 500);
> properties.setInt("raft.server.rpc.timeout.max", 600);
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (RATIS-172) TestBatchAppend fails with timeout

2017-12-17 Thread Tsz Wo Nicholas Sze (JIRA)

 [ 
https://issues.apache.org/jira/browse/RATIS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo Nicholas Sze resolved RATIS-172.
---
   Resolution: Fixed
Fix Version/s: 0.2.0-alpha

I have committed this.  Thanks, Mukul!

> TestBatchAppend fails with timeout
> --
>
> Key: RATIS-172
> URL: https://issues.apache.org/jira/browse/RATIS-172
> Project: Ratis
>  Issue Type: Bug
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Mukul Kumar Singh
> Fix For: 0.2.0-alpha
>
> Attachments: RATIS-172.001.patch
>
>
> After RATIS-161, TestBatchAppend fails with timeout.
> Tried to reset the HEAD to before RATIS-161. TestBatchAppend could pass 
> successfully.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (RATIS-172) TestBatchAppend fails with timeout

2017-12-17 Thread Tsz Wo Nicholas Sze (JIRA)

[ 
https://issues.apache.org/jira/browse/RATIS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294437#comment-16294437
 ] 

Tsz Wo Nicholas Sze commented on RATIS-172:
---

+1 patch looks good.

> TestBatchAppend fails with timeout
> --
>
> Key: RATIS-172
> URL: https://issues.apache.org/jira/browse/RATIS-172
> Project: Ratis
>  Issue Type: Bug
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Mukul Kumar Singh
> Attachments: RATIS-172.001.patch
>
>
> After RATIS-161, TestBatchAppend fails with timeout.
> Tried to reset the HEAD to before RATIS-161. TestBatchAppend could pass 
> successfully.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (RATIS-175) RaftServerProxy should close server rpc in case instance creation fails

2017-12-17 Thread Lokesh Jain (JIRA)
Lokesh Jain created RATIS-175:
-

 Summary: RaftServerProxy should close server rpc in case instance 
creation fails
 Key: RATIS-175
 URL: https://issues.apache.org/jira/browse/RATIS-175
 Project: Ratis
  Issue Type: Bug
Reporter: Lokesh Jain
Assignee: Lokesh Jain


Currently RaftServerProxy does not close the server rpc in case its instance 
creation fails. This leads to BindException when a RaftServerProxy instance 
creation is reattempted in ServerImplUtils#newRaftServer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)