[
https://issues.apache.org/jira/browse/CASSANDRA-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994122#comment-13994122
]
Philip Thompson commented on CASSANDRA-7001:
--------------------------------------------
Summary of manual testing (dtest integration coming. See CASSANDRA-7202):
All functionality was tested by running the .bat files through cmd and
powershell, on both Windows 7 and Windows Server 2008.
All of the command line arguments were functional (foreground, background, -p,
-H, -E, -verbose, -help).
System still started up correctly if invalid paths for output files were
specified, but warning messages were displayed. An issue was found with the -p
command line argument, which was fixed in v3 of the patch.
Heap and new-gen memory were correctly set based on system memory (according to
rules defined in comments in cassandra.ps1). The .bat file correctly handles
problems with powershell shell file execution policy.
For stop-server.bat, all command line arguments were tested, in both cmd and
powershell, on both Windows 7 and Windows Server 2008. Stop-server.bat
correctly handles receving invalid pid files, as well as valid pid-files but
invalid pid's.
It should be noted that CASSANDRA-7202 is tracking improving ccm compatibility
with this patch, at which point the bootstrap tests will be an effective test
for this patch, with a few modifications. It will also ensure that Cassandra is
fully functional using these startup scripts.
> Windows launch feature parity - augment launch process using PowerShell to
> match capabilities of *nix launching
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7001
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Joshua McKenzie
> Assignee: Joshua McKenzie
> Labels: qa-resolved
> Fix For: 2.1 rc1
>
> Attachments: 7001_v1.txt, 7001_v2.txt, 7001_v3.txt
>
>
> The current .bat-based launching has neither the logic nor robustness of a
> bash or PowerShell-based solution. In pursuit of making Windows a 1st-class
> citizen for C*, we need to augment the launch-process using something like
> PowerShell to get as close to feature-parity as possible with Linux.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
