On Fri, Jan 25, 2013 at 7:59 PM, Michael Reynolds wrote:
> João, I don't see where the "very bad performance" would happen if we
> were to use a separate solr server. Is your concern the delay
> incurred while spinning up the redundant solr server? Or am I missing
> something?
I believe the per
Thank you both for your helpful replies! So, to summarize:
* Running separate generic apache solr server is doable
* Although ideal approach would be to use solr server 4.0 to take
advantage of the cloud capability, there are compatibility problems
with the index structure of dspace 3.0 that woul
On Fri, Jan 25, 2013 at 5:21 PM, Carlos Walter Blandon Alvarez
wrote:
> We have DSPACE 1.8 version and we will to install 3.0 version in other server.
>
> Can we restore the database version to 1.8 to 3.0?
> What other files and configuration are recommended to move?
Hi Carlos,
yes, you can res
Hi all.We have DSPACE 1.8 version and we will to install 3.0 version in other server.Can we restore the database version to 1.8 to 3.0?What other files and configuration are recommended to move?Regards,Walter BlandónAnalista TécnicoCentro Cultural Biblioteca "Luis Echavarría Villegas"Tel: (57) (4)
Hello,
yes this is reproducable using different names in dspace.hostname and
dspace.baseUrl. Check your build.properties for these values.
Maybe you got
dspace.hostname = localhost
and
dspace.baseUrl = http://just.something.different
A setting which further influences this is the dspace.cfg set
On Thu, Jan 24, 2013 at 9:04 AM, mErRYo wrote:
> Hi all, I am using dspace 3.0 with jspui & discovery. I am facing problem
> when i click on feedback page. Problem is when a anonymous user clicks on
> this page link it ask for username and password (that is redirect to
> password login page). Whi
On Fri, Jan 25, 2013 at 2:42 PM, Miguel Angel Robledo
wrote:
> I come from old versions of dspace and now i have 1.8.2 in a production
> environment and 3.0 in a development environment. I have the following
> cron jobs but i don know if it is necessary
>
> 0 1 *** [dspace]/ bin / dspace stat-gene
Hi,
I come from old versions of dspace and now i have 1.8.2 in a production
environment and 3.0 in a development environment. I have the following
cron jobs but i don know if it is necessary
0 1 *** [dspace]/ bin / dspace stat-general
0 1 *** [dspace]/ bin / dspace stat-monthly
0 2 *** [dspace]
Hi João,
I suspect that it might be a side-effect of the problem mentioned in
this thread and jira issue:
http://comments.gmane.org/gmane.comp.db.dspace.user/18148
https://jira.duraspace.org/browse/DS-1458
Can you verify that there's a lot of " in transaction" processes
when you list processes u
Hello,
We are having a problem related to the Dspace increasing the number of
file descriptors when making connections to the database and not
releasing them. Thus, we get a lot of idle connections in the database
until it reaches the maximum number of file descriptors. As consequence,
it star
Ok. My last error came thru at: 10h00 approx
>>>
25 Jan 2013 10:19:49 AM org.apache.solr.common.SolrException log
<<<
Lets see what happens later.
On 25 January 2013 12:24, helix84 wrote:
> I haven't noticed any problem there. The fact that it's a facet
> (subject_filter) suggests that the offe
I just tried VisualVM (the screenshot I linked) and it is extremely easy to use.
But I'm not sure anymore that it will help because if I filter the
heap for class names containing "dspace" (this includes the package
name), all those classes are small (< 0.1 % size). The classes taking
up most memo
I haven't noticed any problem there. The fact that it's a facet
(subject_filter) suggests that the offending character is in the data,
not in a query given by the user, so it puzzles me that I didn't find
anything. Are you able to reproduce the problem after running
update-discovery-index? A way to
Thx Ivan. Anybody else got tool suggestions?
On 25 January 2013 12:04, helix84 wrote:
> On Fri, Jan 25, 2013 at 10:41 AM, Hilton Gibson
> wrote:
> > Since upgrading to DSpace 1.8.2 in Dec/Jan the memory is climbing
> radically.
> > Does anybody else experience this. What can cause it?
>
> I do
On Fri, Jan 25, 2013 at 10:41 AM, Hilton Gibson wrote:
> Since upgrading to DSpace 1.8.2 in Dec/Jan the memory is climbing radically.
> Does anybody else experience this. What can cause it?
I don't know, if I knew I would have reported it as a bug :)
But here's how I would proceed. I would find
On Fri, Jan 25, 2013 at 10:38 AM, Hilton Gibson wrote:
> Can someone tell me why this is a SEVERE error. Thx.
>
> SEVERE: org.apache.solr.common.SolrException:
> org.apache.lucene.queryParser.ParseException: Cannot parse
> 'subject_filter:team\': Lexical error at line 1, column 21. Encountere
Can someone tell me why this is a SEVERE error. Thx.
>>>
SEVERE: org.apache.solr.common.SolrException:
org.apache.lucene.queryParser.ParseException: Cannot parse
'subject_filter:team\': Lexical error at line 1, column 21. Encountered:
after : ""
at
org.apache.solr.handler.component.QueryComponent
17 matches
Mail list logo
