You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2009/06/05 20:33:07 UTC
[jira] Created: (CASSANDRA-219) weakreadremote has high response
return (>100ms)
weakreadremote has high response return (>100ms)
-------------------------------------------------
Key: CASSANDRA-219
URL: https://issues.apache.org/jira/browse/CASSANDRA-219
Project: Cassandra
Issue Type: Bug
Affects Versions: trunk, 0.3
Reporter: Chris Goffinet
Fix For: trunk, 0.3
When a client makes a request to a node where data does not live, it tries to fetch from a remote node. We noticed that in some JDK's the select() has very strange bugs. Right now under:
src/java/org/apache/cassandra/net/SelectorManager.java
run() {
..
select(100) should be changed to select(1);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-219) weakreadremote has high response
return (>100ms)
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-219:
-------------------------------------
Fix Version/s: (was: 0.4)
0.3
> weakreadremote has high response return (>100ms)
> -------------------------------------------------
>
> Key: CASSANDRA-219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-219
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Chris Goffinet
> Assignee: Jonathan Ellis
> Fix For: 0.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When a client makes a request to a node where data does not live, it tries to fetch from a remote node. We noticed that in some JDK's the select() has very strange bugs. Right now under:
> src/java/org/apache/cassandra/net/SelectorManager.java
> run() {
> ..
> select(100) should be changed to select(1);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-219) weakreadremote has high response
return (>100ms)
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716718#action_12716718 ]
Jonathan Ellis commented on CASSANDRA-219:
------------------------------------------
committed to 0.3 and trunk
> weakreadremote has high response return (>100ms)
> -------------------------------------------------
>
> Key: CASSANDRA-219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-219
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: trunk, 0.3
> Reporter: Chris Goffinet
> Fix For: trunk, 0.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When a client makes a request to a node where data does not live, it tries to fetch from a remote node. We noticed that in some JDK's the select() has very strange bugs. Right now under:
> src/java/org/apache/cassandra/net/SelectorManager.java
> run() {
> ..
> select(100) should be changed to select(1);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-219) weakreadremote has high response
return (>100ms)
Posted by "Chris Goffinet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Goffinet resolved CASSANDRA-219.
--------------------------------------
Resolution: Fixed
> weakreadremote has high response return (>100ms)
> -------------------------------------------------
>
> Key: CASSANDRA-219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-219
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: trunk, 0.3
> Reporter: Chris Goffinet
> Fix For: trunk, 0.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When a client makes a request to a node where data does not live, it tries to fetch from a remote node. We noticed that in some JDK's the select() has very strange bugs. Right now under:
> src/java/org/apache/cassandra/net/SelectorManager.java
> run() {
> ..
> select(100) should be changed to select(1);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CASSANDRA-219) weakreadremote has high response
return (>100ms)
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-219:
----------------------------------------
Assignee: Jonathan Ellis
> weakreadremote has high response return (>100ms)
> -------------------------------------------------
>
> Key: CASSANDRA-219
> URL: https://issues.apache.org/jira/browse/CASSANDRA-219
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Chris Goffinet
> Assignee: Jonathan Ellis
> Fix For: 0.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When a client makes a request to a node where data does not live, it tries to fetch from a remote node. We noticed that in some JDK's the select() has very strange bugs. Right now under:
> src/java/org/apache/cassandra/net/SelectorManager.java
> run() {
> ..
> select(100) should be changed to select(1);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.