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

Mark Miller updated SOLR-1873:
------------------------------

    Attachment: SOLR-1873.patch
                zookeeper-3.3.1.jar

I've been meaning to upload this for a couple days - here is my latest:

I've updated to trunk.
I've updated to the latest ZooKeeper so that tests can properly shut down and 
not leave large tmp dirs on Windows.
I've cleaned up and improved some of the cloud tests.

The main issue I see at the moment is that the shutdown is not completely clean 
and so some errors get pumped to std err that should be ignored - this is more 
of a visual issue at the moement.
I'd like to take care of that if I can. However, first I want to see how this 
fairs on Roberts Windows machine. Have to figure out if the reconnect is still 
a problem.

- Mark

> Commit Solr Cloud to trunk
> --------------------------
>
>                 Key: SOLR-1873
>                 URL: https://issues.apache.org/jira/browse/SOLR-1873
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.4
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: Next
>
>         Attachments: log4j-over-slf4j-1.5.5.jar, SOLR-1873.patch, 
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, 
> SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, SOLR-1873.patch, 
> zookeeper-3.2.2.jar, zookeeper-3.3.1.jar
>
>
> This is a real hassle - I didn't merge up to trunk before all the svn 
> scrambling, so integrating cloud is now a bit difficult. I'm running through 
> and just preparing a commit by hand though (applying changes/handling 
> conflicts a file at a time).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to