[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2014-01-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867170#comment-13867170
 ] 

ASF subversion and git services commented on SOLR-5543:
---

Commit 1556969 from [~elyograg] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1556969 ]

SOLR-5543: Move changes entry from 4.7.0 to 4.6.1 (merge trunk r1556968)

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 5.0, 4.7, 4.6.1
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2014-01-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867167#comment-13867167
 ] 

ASF subversion and git services commented on SOLR-5543:
---

Commit 1556968 from [~elyograg] in branch 'dev/trunk'
[ https://svn.apache.org/r1556968 ]

SOLR-5543: move changes entry from 4.7.0 to 4.6.1.

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2014-01-09 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867155#comment-13867155
 ] 

ASF subversion and git services commented on SOLR-5543:
---

Commit 1556965 from [~elyograg] in branch 'dev/branches/lucene_solr_4_6'
[ https://svn.apache.org/r1556965 ]

SOLR-5543: Backport to 4.6 branch, for 4.6.1 release.

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2014-01-09 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867142#comment-13867142
 ] 

Shawn Heisey commented on SOLR-5543:


With a verbal OK from [~markrmil...@gmail.com] via IRC, I am backporting the 
fix for this issue to 4.6.1.

Both precommit and tests in solr/ are passing.  The commits for trunk and 
branch_4x have no code changes, I'm just moving the CHANGES.txt entry.


> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2013-12-17 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851329#comment-13851329
 ] 

Shawn Heisey commented on SOLR-5543:


The reason I think it's critical to include in 4.6.1 is this:  Although 
everything works perfectly after the problem appears, as soon as you restart 
Solr, the duplicate entries cause exceptions and cores don't start up properly. 
 That was my experience when I upgraded my dev server to the released 4.6.0, 
rebuilt the index (resulting in seven core swaps), and then later restarted 
Solr for some config changes.  It's not standard procedure to restart Solr 
after rebuilding, but it does occasionally happen.  It happens a LOT on my dev 
server, where I try out new configs.

If I were to do a PERSIST CoreAdmin action after each swap, would it 
effectively fix the problem even on an unpatched 4.6.0?

TL;DR: I do have the ability to instead do a "persist all" after all of the 
swaps, because I separately create and track per-server objects for CoreAdmin 
SolrJ calls.  Although I end up with 28 HttpSolrServer objects for updates and 
queries with my production build application, I only create one CoreAdmin 
server object for each host/port combination, instead of an additional 28 
objects.  I don't know what the incremental size of HttpSolrServer objects is, 
but I do try to be careful about memory.


> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2013-12-17 Thread Alan Woodward (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850591#comment-13850591
 ] 

Alan Woodward commented on SOLR-5543:
-

It doesn't seem to actually make a difference to the running application, 
because the ConfigSolr object deduplicates the entries internally, which is 
also why it only writes out the latest swap (the current set, plus the two 
extra core definitions).  But it makes it confusing for people who are editing 
solr.xml offline.

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2013-12-17 Thread Shawn Heisey (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850584#comment-13850584
 ] 

Shawn Heisey commented on SOLR-5543:


[~romseygeek] ... I hear we're doing a 4.6.1 in the near future.  IMHO this is 
a strong candidate for backporting.

Interesting detail, which I don't think needs to change your patch at all:  My 
'full index rebuild' process does seven core swaps.  It appears that the 
duplication introduced by a core swap is eliminated by a subsequent core swap 
-- there were only extra entries for the last core swapped.


> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2013-12-14 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848457#comment-13848457
 ] 

ASF subversion and git services commented on SOLR-5543:
---

Commit 1550970 from [~romseygeek] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1550970 ]

SOLR-5543: Core Swaps result in duplicate entries in solr.xml

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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



[jira] [Commented] (SOLR-5543) solr.xml duplicat eentries after SWAP 4.6

2013-12-14 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848456#comment-13848456
 ] 

ASF subversion and git services commented on SOLR-5543:
---

Commit 1550969 from [~romseygeek] in branch 'dev/trunk'
[ https://svn.apache.org/r1550969 ]

SOLR-5543: Core Swaps result in duplicate entries in solr.xml

> solr.xml duplicat eentries after SWAP 4.6
> -
>
> Key: SOLR-5543
> URL: https://issues.apache.org/jira/browse/SOLR-5543
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 4.6
>Reporter: Bill Bell
>Assignee: Alan Woodward
> Fix For: 4.7
>
> Attachments: SOLR-5543.patch
>
>
> We are having issues with SWAP CoreAdmin in 4.6.
> Using legacy solr.xml we issue a COreodmin SWAP, and we want it persistent. 
> It has been running flawless since 4.5. Now it creates duplicate lines in 
> solr.xml.
> Even the example multi core schema in doesn't work with persistent="true" - 
> it creates duplicate lines in solr.xml.
>  
>  transient="false"/>
>  instanceDir="citystateprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="inactiveproviders" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="portalprovider" transient="false"/>
>  transient="false"/>
>  transient="false"/>
>  instanceDir="providersearch" transient="false"/>
>  instanceDir="tridioncomponents" transient="false"/>
>  transient="false"/>
>  loadOnStartup="true" transient="false"/>
> 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

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