You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Wei Li (JIRA)" <ji...@apache.org> on 2009/11/18 23:00:39 UTC
[jira] Created: (CASSANDRA-561) Cassandra Simulator
Cassandra Simulator
-------------------
Key: CASSANDRA-561
URL: https://issues.apache.org/jira/browse/CASSANDRA-561
Project: Cassandra
Issue Type: Improvement
Affects Versions: 0.4
Environment: RHEL 4.X, 5.X
Reporter: Wei Li
Fix For: 0.4
Motivations:
=========
Cassandra is a distributed system. This nature makes it harder for developers and testers to rapidly develop and test applications without proper hardware and network setups. It is particular hard for testing, when we want to know how system behaves under stressed network conditions, hardware changes and failures, and many other scenarios. The motivations of the building a Cassandra simulator is to provide a tool to simplify procedures to achieve above needs.
Requirements:
===========
Simulator is a separate project from Canssandra main project. It does not insert and/or modify any code in Cassandra main project, rather it operates as an additional service in Cassandra node(See enclosed doc for details). Simulator can be started in two modes: Simulated mode and "pure" Cassandra mode. The design Requirements of the simulator are:
* To simulate multiple node operations within single linux box
* To simulate Hardware conditions, such as adding new nodes, node out of service, etc.
* To simulate network conditions, message delays, drops, etc.
* To carry out read/write operations at the simulated environment
* To provide APIs to access logging information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-561) Cassandra Simulator
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-561:
-------------------------------------
Component/s: Contrib
Fix Version/s: (was: 0.4)
Affects Version/s: (was: 0.4)
> Cassandra Simulator
> -------------------
>
> Key: CASSANDRA-561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-561
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Environment: RHEL 4.X, 5.X
> Reporter: Wei Li
> Attachments: simulator.zip.gz, simulatorDoc.zip.gz
>
>
> Motivations:
> =========
> Cassandra is a distributed system. This nature makes it harder for developers and testers to rapidly develop and test applications without proper hardware and network setups. It is particular hard for testing, when we want to know how system behaves under stressed network conditions, hardware changes and failures, and many other scenarios. The motivations of the building a Cassandra simulator is to provide a tool to simplify procedures to achieve above needs.
> Requirements:
> ===========
> Simulator is a separate project from Canssandra main project. It does not insert and/or modify any code in Cassandra main project, rather it operates as an additional service in Cassandra node(See enclosed doc for details). Simulator can be started in two modes: Simulated mode and "pure" Cassandra mode. The design Requirements of the simulator are:
> * To simulate multiple node operations within single linux box
> * To simulate Hardware conditions, such as adding new nodes, node out of service, etc.
> * To simulate network conditions, message delays, drops, etc.
> * To carry out read/write operations at the simulated environment
> * To provide APIs to access logging information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-561) Cassandra Simulator
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786190#action_12786190 ]
Stu Hood commented on CASSANDRA-561:
------------------------------------
Wei: thank you very much for your contribution! This is quite a chunk of code, and it will be a while before any of the Casandra committers fully understand it.
Was your intention that the simulator should be merged as a system-test framework for Cassandra (to run along with the unit tests in continuous integration), or that it be merged to contrib/, where people who were interested in researching Cassandra's distribution could run experiments manually?
Also, if this code were to be merged, would you be able to continue maintaining it?
Thanks again!
> Cassandra Simulator
> -------------------
>
> Key: CASSANDRA-561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-561
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Environment: RHEL 4.X, 5.X
> Reporter: Wei Li
> Attachments: simulator.zip.gz, simulatorDoc.zip.gz
>
>
> Motivations:
> =========
> Cassandra is a distributed system. This nature makes it harder for developers and testers to rapidly develop and test applications without proper hardware and network setups. It is particular hard for testing, when we want to know how system behaves under stressed network conditions, hardware changes and failures, and many other scenarios. The motivations of the building a Cassandra simulator is to provide a tool to simplify procedures to achieve above needs.
> Requirements:
> ===========
> Simulator is a separate project from Canssandra main project. It does not insert and/or modify any code in Cassandra main project, rather it operates as an additional service in Cassandra node(See enclosed doc for details). Simulator can be started in two modes: Simulated mode and "pure" Cassandra mode. The design Requirements of the simulator are:
> * To simulate multiple node operations within single linux box
> * To simulate Hardware conditions, such as adding new nodes, node out of service, etc.
> * To simulate network conditions, message delays, drops, etc.
> * To carry out read/write operations at the simulated environment
> * To provide APIs to access logging information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-561) Cassandra Simulator
Posted by "Wei Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791135#action_12791135 ]
Wei Li commented on CASSANDRA-561:
----------------------------------
Stu,
Thank you very much for your email. Sorry for the late reply.
Yes, the Cassandra simulator is a quite chunk of code. It is mostly the result of two persons' work, jim Yang (sjimmyyang@yahoo.com) and myself. Both of us currently are Yahoo employees.
Our initially intention is that the developers can develop their unit tests on simulator without complication of hardware and network setups. Eventually we want to be integrated into company's CI testing framework. But we are not there yet.
Currently, the Cassandra simulator can simulate multiple Cassandra nodes in same box (with multiple jvms). it can simulate adding and taking down nodes, and simulate network hiccups by delaying message deliveries among the nodes.
Although sometimes we would be busier than other time with our projects, yes we would be happy to support and maintain the code whenever we have time.
Best.
Wei
> Cassandra Simulator
> -------------------
>
> Key: CASSANDRA-561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-561
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Environment: RHEL 4.X, 5.X
> Reporter: Wei Li
> Attachments: simulator.zip.gz, simulatorDoc.zip.gz
>
>
> Motivations:
> =========
> Cassandra is a distributed system. This nature makes it harder for developers and testers to rapidly develop and test applications without proper hardware and network setups. It is particular hard for testing, when we want to know how system behaves under stressed network conditions, hardware changes and failures, and many other scenarios. The motivations of the building a Cassandra simulator is to provide a tool to simplify procedures to achieve above needs.
> Requirements:
> ===========
> Simulator is a separate project from Canssandra main project. It does not insert and/or modify any code in Cassandra main project, rather it operates as an additional service in Cassandra node(See enclosed doc for details). Simulator can be started in two modes: Simulated mode and "pure" Cassandra mode. The design Requirements of the simulator are:
> * To simulate multiple node operations within single linux box
> * To simulate Hardware conditions, such as adding new nodes, node out of service, etc.
> * To simulate network conditions, message delays, drops, etc.
> * To carry out read/write operations at the simulated environment
> * To provide APIs to access logging information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-561) Cassandra Simulator
Posted by "Wei Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei Li updated CASSANDRA-561:
-----------------------------
Attachment: simulatorDoc.zip.gz
simulator.zip.gz
1). Simulator source code
2). Simulator documentations
> Cassandra Simulator
> -------------------
>
> Key: CASSANDRA-561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-561
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.4
> Environment: RHEL 4.X, 5.X
> Reporter: Wei Li
> Fix For: 0.4
>
> Attachments: simulator.zip.gz, simulatorDoc.zip.gz
>
>
> Motivations:
> =========
> Cassandra is a distributed system. This nature makes it harder for developers and testers to rapidly develop and test applications without proper hardware and network setups. It is particular hard for testing, when we want to know how system behaves under stressed network conditions, hardware changes and failures, and many other scenarios. The motivations of the building a Cassandra simulator is to provide a tool to simplify procedures to achieve above needs.
> Requirements:
> ===========
> Simulator is a separate project from Canssandra main project. It does not insert and/or modify any code in Cassandra main project, rather it operates as an additional service in Cassandra node(See enclosed doc for details). Simulator can be started in two modes: Simulated mode and "pure" Cassandra mode. The design Requirements of the simulator are:
> * To simulate multiple node operations within single linux box
> * To simulate Hardware conditions, such as adding new nodes, node out of service, etc.
> * To simulate network conditions, message delays, drops, etc.
> * To carry out read/write operations at the simulated environment
> * To provide APIs to access logging information
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.