[jira] [Updated] (RATIS-176) Log Appender should throw an Exception in case append entry size exceeds the maxBufferSize configured

2017-12-19 Thread Shashikant Banerjee (JIRA) 

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

Shashikant Banerjee updated RATIS-176:
--
Description: LogAppender while adding append entry in LogEntryBuffer, 
checks whether the total allocated for all entries does not exceed the 
maxBufferSize allocated. In case, the size exceeds the limit ,entries are not 
added to the buffer but no exception is thrown . This case needs to be handled. 
 (was: LogAppender while adding append entry in LogEntryBuffer, checks whether 
the total allocated for all entries does not exceed the maxBufferSize 
allocated. In case, the size exceeds the limit ,
entries are not added to the buffer but no exception is thrown . This case 
needs to be handled.)

> Log Appender should throw an Exception in case  append entry size exceeds the 
> maxBufferSize configured
> --
>
> Key: RATIS-176
> URL: https://issues.apache.org/jira/browse/RATIS-176
> Project: Ratis
>  Issue Type: Bug
>Reporter: Shashikant Banerjee
>Assignee: Shashikant Banerjee
>
> LogAppender while adding append entry in LogEntryBuffer, checks whether the 
> total allocated for all entries does not exceed the maxBufferSize allocated. 
> In case, the size exceeds the limit ,entries are not added to the buffer but 
> no exception is thrown . This case needs to be handled.



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

[jira] [Created] (RATIS-176) Log Appender should throw an Exception in case append entry size exceeds the maxBufferSize configured

2017-12-19 Thread Shashikant Banerjee (JIRA) 
Shashikant Banerjee created RATIS-176:
-

 Summary: Log Appender should throw an Exception in case  append 
entry size exceeds the maxBufferSize configured
 Key: RATIS-176
 URL: https://issues.apache.org/jira/browse/RATIS-176
 Project: Ratis
  Issue Type: Bug
Reporter: Shashikant Banerjee
Assignee: Shashikant Banerjee


LogAppender while adding append entry in LogEntryBuffer, checks whether the 
total allocated for all entries does not exceed the maxBufferSize allocated. In 
case, the size exceeds the limit ,
entries are not added to the buffer but no exception is thrown . This case 
needs to be handled.



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

[jira] [Updated] (RATIS-5) Setup website

2017-12-19 Thread Elek, Marton (JIRA) 

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

Elek, Marton updated RATIS-5:
-
Attachment: ratis-rendered.tar.gz

I also uploaded the final rendered site to make it easier to check.

> Setup website
> -
>
> Key: RATIS-5
> URL: https://issues.apache.org/jira/browse/RATIS-5
> Project: Ratis
>  Issue Type: Task
>Reporter: Enis Soztutar
>Assignee: Elek, Marton
> Attachments: RATIS-5.001.patch, RATIS-5.002.patch, 
> ratis-rendered.tar.gz
>
>
> A project website is needed. Possibly, we can use bootstrap and fork already 
> existing syles. 
> https://phoenix.apache.org/
> https://hbase.apache.org/
> https://cassandra.apache.org/
> Since Ratis is a podling it will be
>   https://ratis.incubator.apache.org/



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

[jira] [Commented] (RATIS-140) Raft client should reuse the gRPC stream for all async calls

2017-12-19 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on RATIS-140:
-

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
6s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
8s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
30s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
5s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
49s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}  
0m 20s{color} | {color:orange} root: The patch generated 201 new + 283 
unchanged - 24 fixed = 484 total (was 307) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
30s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}  7m 53s{color} 
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
 7s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 13m 43s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | ratis.hadooprpc.TestRetryCacheWithHadoopRpc |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/ratis:date2017-12-19 
|
| JIRA Issue | RATIS-140 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12902815/r140_20171219.patch |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  checkstyle  
compile  |
| uname | Linux c20550c298ec 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 
11:55:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-RATIS-Build/yetus-personality.sh
 |
| git revision | master / ce3afb0 |
| Default Java | 1.8.0_151 |
| checkstyle | 
https://builds.apache.org/job/PreCommit-RATIS-Build/71/artifact/out/diff-checkstyle-root.txt
 |
| unit | 
https://builds.apache.org/job/PreCommit-RATIS-Build/71/artifact/out/patch-unit-root.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-RATIS-Build/71/testReport/ |
| modules | C: ratis-common ratis-client ratis-server ratis-grpc U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-RATIS-Build/71/console |
| Powered by | Apache Yetus 0.5.0   http://yetus.apache.org |


This message was automatically generated.



> Raft client should reuse the gRPC stream for all async calls
> 
>
> Key: RATIS-140
> URL: https://issues.apache.org/jira/browse/RATIS-140
> Project: Ratis
>  Issue Type: Bug
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
> Attachments: r140_20171123.patch,

[jira] [Updated] (RATIS-140) Raft client should reuse the gRPC stream for all async calls

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

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

Tsz Wo Nicholas Sze updated RATIS-140:
--
Attachment: r140_20171219.patch

Jing, thanks a lot for the review!

I agree that the sliding window should be able to limit the request.  Let's 
move the semaphore to the sliding window in a separated JIRA.

r140_20171219.patch: addresses Jing's comments.

> Raft client should reuse the gRPC stream for all async calls
> 
>
> Key: RATIS-140
> URL: https://issues.apache.org/jira/browse/RATIS-140
> Project: Ratis
>  Issue Type: Bug
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
> Attachments: r140_20171123.patch, r140_20171124.patch, 
> r140_20171125.patch, r140_20171126.patch, r140_20171126b.patch, 
> r140_20171130.patch, r140_20171203.patch, r140_20171204.patch, 
> r140_20171206.patch, r140_20171210.patch, r140_20171219.patch
>
>
> Async client is being added in RATIS-113.  However, we found that the server 
> side (RaftClientProtocolService) may see out-of-order grpc messages even if 
> all messages are sent by the same client.



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