Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <13106334.post@talk.nabble.com>
Date: Mon, 8 Oct 2007 15:44:13 -0700 (PDT)
From: William Louth <william.louth@jinspired.com>
To: dev@jackrabbit.apache.org
Subject: Re: Is this issue resolved?
In-Reply-To: <8fd002c60710081523m538807c2lc91ba943fd99e52a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <8fd002c60710030502h2d6c1d59q957c353811a0c14e@mail.gmail.com>
 <510143ac0710030536s5b3adf3m9d475299a3511f8a@mail.gmail.com>
 <13099553.post@talk.nabble.com> <470A8205.7010902@wasabicowboy.com>
 <13104910.post@talk.nabble.com>
 <8fd002c60710081523m538807c2lc91ba943fd99e52a@mail.gmail.com>


Hi,

I really do not want to create such an bad impression of the work of the
team. There are transactional issues that need to addressed some are easier
and others more architectural. I think it really comes down to a trade-off
between ease of use (JCR is a nice storage agnostic API) and enterprise
'ilities such as reliability. Every software (and vendor) selection involves
risk management but the level of risk is something you must decided in terms
of operating environment. 

In a non-clustered environment the product work and was extremely ease to
setup and get a flying start. When it came to heavy workloads and
fault-tolerance in a clustered environment that is when we started having
doubts at least in the performance tests I was involved in. 

To be honest the customer has migrated over to the EXO platform but
everything is not so perfect there either. That said the clustering appears
must more reliable but I am worried about speed of rebuilding Lucene indexes
when a node in the cluster becomes disconnected as there is no event
log/journal like in JackRabbit. At this stage in the quality of JCR
implementations its like "picking your own poison".

regards,

William


Peter Travas wrote:
> 
> William,
> 
> Thanks for answering in this thread. Have you filled JIRA issues reporting
> problems encountered during your tests? Looks like you spent a lot of time
> on this. Can you, with your experience on the HA and transaction
> processing
> field, help with these issues?
> Your blog entry (and some comments about poor scalability on TSS thread
> provided by Jukka) are killing my overall good impression on JR and JCR.
> 
> I'm responsible for making decision whether JR in a go or no-go for my
> project and, to be honest, after this bad press I'm simply afraid of being
> hanged by my teammates in the near future, if such scalability problems
> would appear.
> 
> We had some _extremely_ bad experiences with another Apache project, so my
> team is a little bit touchy on this field :(:(:(:(.
> 
> 

-- 
View this message in context: http://www.nabble.com/Is-this-issue-resolved--tf4561381.html#a13106334
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.