[jira] [Updated] (CASSANDRA-14836) Incorrect log entry during startup in 4.0

2018-11-15 Thread C. Scott Andreas (JIRA)


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

C. Scott Andreas updated CASSANDRA-14836:
-
Component/s: Lifecycle

> Incorrect log entry during startup in 4.0
> -
>
> Key: CASSANDRA-14836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14836
> Project: Cassandra
>  Issue Type: Bug
>  Components: Lifecycle
>Reporter: Tommy Stendahl
>Assignee: Tommy Stendahl
>Priority: Trivial
>
> When doing some testing on 4.0 I found this in the log:
> {noformat}
> 2018-10-12T14:06:14.507+0200  INFO [main] 
> StartupClusterConnectivityChecker.java:113 After waiting/processing for 10005 
> milliseconds, 1 out of 3 peers (0.0%) have been marked alive and had 
> connections established{noformat}
> 1 out of 3 is not 0%:)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14836) Incorrect log entry during startup in 4.0

2018-10-23 Thread Ariel Weisberg (JIRA)


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

Ariel Weisberg updated CASSANDRA-14836:
---
Resolution: Fixed
Status: Resolved  (was: Ready to Commit)

Committed as 
[c3ef43d45e5c9c44f22dbeb8a58232aa6f0cfd15|https://github.com/apache/cassandra/commit/c3ef43d45e5c9c44f22dbeb8a58232aa6f0cfd15]
 thanks!

> Incorrect log entry during startup in 4.0
> -
>
> Key: CASSANDRA-14836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14836
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Tommy Stendahl
>Assignee: Tommy Stendahl
>Priority: Trivial
>
> When doing some testing on 4.0 I found this in the log:
> {noformat}
> 2018-10-12T14:06:14.507+0200  INFO [main] 
> StartupClusterConnectivityChecker.java:113 After waiting/processing for 10005 
> milliseconds, 1 out of 3 peers (0.0%) have been marked alive and had 
> connections established{noformat}
> 1 out of 3 is not 0%:)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14836) Incorrect log entry during startup in 4.0

2018-10-23 Thread Ariel Weisberg (JIRA)


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

Ariel Weisberg updated CASSANDRA-14836:
---
Status: Ready to Commit  (was: Patch Available)

> Incorrect log entry during startup in 4.0
> -
>
> Key: CASSANDRA-14836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14836
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Tommy Stendahl
>Assignee: Tommy Stendahl
>Priority: Trivial
>
> When doing some testing on 4.0 I found this in the log:
> {noformat}
> 2018-10-12T14:06:14.507+0200  INFO [main] 
> StartupClusterConnectivityChecker.java:113 After waiting/processing for 10005 
> milliseconds, 1 out of 3 peers (0.0%) have been marked alive and had 
> connections established{noformat}
> 1 out of 3 is not 0%:)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14836) Incorrect log entry during startup in 4.0

2018-10-23 Thread Ariel Weisberg (JIRA)


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

Ariel Weisberg updated CASSANDRA-14836:
---
Reviewer: Ariel Weisberg

> Incorrect log entry during startup in 4.0
> -
>
> Key: CASSANDRA-14836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14836
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Tommy Stendahl
>Assignee: Tommy Stendahl
>Priority: Trivial
>
> When doing some testing on 4.0 I found this in the log:
> {noformat}
> 2018-10-12T14:06:14.507+0200  INFO [main] 
> StartupClusterConnectivityChecker.java:113 After waiting/processing for 10005 
> milliseconds, 1 out of 3 peers (0.0%) have been marked alive and had 
> connections established{noformat}
> 1 out of 3 is not 0%:)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14836) Incorrect log entry during startup in 4.0

2018-10-23 Thread Tommy Stendahl (JIRA)


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

Tommy Stendahl updated CASSANDRA-14836:
---
Status: Patch Available  (was: Open)

> Incorrect log entry during startup in 4.0
> -
>
> Key: CASSANDRA-14836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14836
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Tommy Stendahl
>Assignee: Tommy Stendahl
>Priority: Trivial
>
> When doing some testing on 4.0 I found this in the log:
> {noformat}
> 2018-10-12T14:06:14.507+0200  INFO [main] 
> StartupClusterConnectivityChecker.java:113 After waiting/processing for 10005 
> milliseconds, 1 out of 3 peers (0.0%) have been marked alive and had 
> connections established{noformat}
> 1 out of 3 is not 0%:)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org