You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Warner Onstine <wo...@vmsinfo.com> on 2008/09/29 23:13:39 UTC
clustering doesn't appear to be
I really am not sure what is going on here as things appear to be
working (according to the logs), but unfortunately I can't see stuff
from one node to a different node.
I have two machines setup, each with their own nodes. They are both
connecting to the same db, and when I fired up the second node
everything seemed fine as the second node synced up with the first one.
I then decided to mount this node (2) (I'm using WebDAV for my
interface so I'm mounting it that way). I pushed up some new files and
in the log files of both nodes I can see them syncing with each other.
Node 2:
2008-09-29 17:03:18,200 INFO [ClusterNode] Appended revision: 1918
2008-09-29 17:03:18,592 INFO [ClusterNode] Appended revision: 1919
2008-09-29 17:03:18,939 INFO [ClusterNode] Appended revision: 1920
2008-09-29 17:03:23,230 INFO [ClusterNode] Appended revision: 1923
2008-09-29 17:03:23,681 INFO [ClusterNode] Appended revision: 1924
2008-09-29 17:03:24,017 INFO [ClusterNode] Appended revision: 1925
Node 1:
2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
'1917' created by this journal, skipped.
2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
'1918' created by this journal, skipped.
2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
'1919' created by this journal, skipped.
2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
'1920' created by this journal, skipped.
2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
'1921' created by this journal, skipped.
2008-09-29 17:03:22,466 INFO [AbstractJournal] Synchronized to
revision: 1921
2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
'1922' created by this journal, skipped.
2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
'1923' created by this journal, skipped.
2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
'1924' created by this journal, skipped.
2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
'1925' created by this journal, skipped.
2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
'1926' created by this journal, skipped.
2008-09-29 17:03:27,473 INFO [AbstractJournal] Synchronized to
revision: 1926
But when I look at these two nodes separately one has the new content
and one doesn't. Curious, I added new content to node 1 and the same
behavior comes up where I can see the new content I just put up on
node 1, but not on node 2.
Any ideas? This seems to be very odd behavior and I'm not sure if it
has something to do with WebDAV or not.
-warner
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
Ok, weirdness has stopped. I have no idea what happened but for some
reason it hadn't registered the new property. Now it all seems to be
working!
Thanks a bunch for the help I appreciate it.
-warner
On Oct 1, 2008, at 3:23 PM, Warner Onstine wrote:
> Ok, I'm trying to use this new system property and nothing is
> happening (in fact in some ways it's worse one of my repositories
> loses all of it's content alltogether).
>
> How do I tell if my repos have their appropriate cluster ids? I
> can't find anything in the log files and I'm not sure what I would
> breakpoint or dig into to find out (as I'm injecting the repository
> using Spring and the repository is a JCR repo so just an interface
> no concrete impl).
>
> Thanks again.
>
> -warner
>
> On Oct 1, 2008, at 10:39 AM, Warner Onstine wrote:
>
>> Ahh, excellent, I wasn't 100% sure what that reference was to. I
>> will give that a try since we really don't want our repository.xml
>> files sitting somewhere on the file system (if we have to make a
>> change that's a real pain to have to do everywhere and I will
>> invariable forget that it needs to get changed everywhere).
>>
>> -warner
>>
>> On Oct 1, 2008, at 9:13 AM, Alexander Klimetschek wrote:
>>
>>> On Wed, Oct 1, 2008 at 5:15 PM, Warner Onstine
>>> <wo...@vmsinfo.com> wrote:
>>>> Wow, that's, um, special. Any ideas as to when this will get
>>>> rolled into the
>>>> main build?
>>>
>>> As noted in the issue, it will be included in the 1.5 release, which
>>> will take a few months I guess.
>>>
>>> As a workaround you could either extract the repository.xml from
>>> your
>>> war files (which I recommend, because it simplifies server
>>> administration, even if the standard jackrabbit webapp includes it
>>> inside), or remove the cluster id attribute and set the magic system
>>> property "org.apache.jackrabbit.core.cluster.node_id" in your
>>> instances before jackrabbit is started.
>>>
>>> Regards,
>>> Alex
>>>
>>> --
>>> Alexander Klimetschek
>>> alexander.klimetschek@day.com
>>
>
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
Ok, I'm trying to use this new system property and nothing is
happening (in fact in some ways it's worse one of my repositories
loses all of it's content alltogether).
How do I tell if my repos have their appropriate cluster ids? I can't
find anything in the log files and I'm not sure what I would
breakpoint or dig into to find out (as I'm injecting the repository
using Spring and the repository is a JCR repo so just an interface no
concrete impl).
Thanks again.
-warner
On Oct 1, 2008, at 10:39 AM, Warner Onstine wrote:
> Ahh, excellent, I wasn't 100% sure what that reference was to. I
> will give that a try since we really don't want our repository.xml
> files sitting somewhere on the file system (if we have to make a
> change that's a real pain to have to do everywhere and I will
> invariable forget that it needs to get changed everywhere).
>
> -warner
>
> On Oct 1, 2008, at 9:13 AM, Alexander Klimetschek wrote:
>
>> On Wed, Oct 1, 2008 at 5:15 PM, Warner Onstine
>> <wo...@vmsinfo.com> wrote:
>>> Wow, that's, um, special. Any ideas as to when this will get
>>> rolled into the
>>> main build?
>>
>> As noted in the issue, it will be included in the 1.5 release, which
>> will take a few months I guess.
>>
>> As a workaround you could either extract the repository.xml from your
>> war files (which I recommend, because it simplifies server
>> administration, even if the standard jackrabbit webapp includes it
>> inside), or remove the cluster id attribute and set the magic system
>> property "org.apache.jackrabbit.core.cluster.node_id" in your
>> instances before jackrabbit is started.
>>
>> Regards,
>> Alex
>>
>> --
>> Alexander Klimetschek
>> alexander.klimetschek@day.com
>
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
Ahh, excellent, I wasn't 100% sure what that reference was to. I will
give that a try since we really don't want our repository.xml files
sitting somewhere on the file system (if we have to make a change
that's a real pain to have to do everywhere and I will invariable
forget that it needs to get changed everywhere).
-warner
On Oct 1, 2008, at 9:13 AM, Alexander Klimetschek wrote:
> On Wed, Oct 1, 2008 at 5:15 PM, Warner Onstine
> <wo...@vmsinfo.com> wrote:
>> Wow, that's, um, special. Any ideas as to when this will get rolled
>> into the
>> main build?
>
> As noted in the issue, it will be included in the 1.5 release, which
> will take a few months I guess.
>
> As a workaround you could either extract the repository.xml from your
> war files (which I recommend, because it simplifies server
> administration, even if the standard jackrabbit webapp includes it
> inside), or remove the cluster id attribute and set the magic system
> property "org.apache.jackrabbit.core.cluster.node_id" in your
> instances before jackrabbit is started.
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com
Re: clustering doesn't appear to be
Posted by Alexander Klimetschek <ak...@day.com>.
On Wed, Oct 1, 2008 at 5:15 PM, Warner Onstine <wo...@vmsinfo.com> wrote:
> Wow, that's, um, special. Any ideas as to when this will get rolled into the
> main build?
As noted in the issue, it will be included in the 1.5 release, which
will take a few months I guess.
As a workaround you could either extract the repository.xml from your
war files (which I recommend, because it simplifies server
administration, even if the standard jackrabbit webapp includes it
inside), or remove the cluster id attribute and set the magic system
property "org.apache.jackrabbit.core.cluster.node_id" in your
instances before jackrabbit is started.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
Wow, that's, um, special. Any ideas as to when this will get rolled
into the main build? I'm investigating other avenues, but this makes
my life more difficult as we can't have two special builds setup one
for each node. Not to mention the fact that I can't modify the war
file once it's on the server.
-warner
On Sep 30, 2008, at 11:56 PM, Thomas Müller wrote:
> Hi,
>
>> No, they each have their own (configurable) node name. I'm
>> attaching my
>> repository.xml file for you. Thanks for the help, it's greatly
>> appreciated.
>
> You have set cluster id as a system property:
> <Cluster id="${webDAV.clusterNode}">
>
> Unfortunately this doesn't work in Jackrabbit 1.4. See also:
> http://issues.apache.org/jira/browse/JCR-1694
>
> Regards,
> Thomas
Re: clustering doesn't appear to be
Posted by Thomas Müller <th...@day.com>.
Hi,
> No, they each have their own (configurable) node name. I'm attaching my
> repository.xml file for you. Thanks for the help, it's greatly appreciated.
You have set cluster id as a system property:
<Cluster id="${webDAV.clusterNode}">
Unfortunately this doesn't work in Jackrabbit 1.4. See also:
http://issues.apache.org/jira/browse/JCR-1694
Regards,
Thomas
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
No, they each have their own (configurable) node name. I'm attaching
my repository.xml file for you. Thanks for the help, it's greatly
appreciated.
-warner
Re: clustering doesn't appear to be
Posted by Thomas Müller <th...@day.com>.
Hi,
Could you check if the cluster ids are the same on both cluster nodes?
The cluster id is supposed to be unique. If this is not the problem,
could you post both repository.xml files?
Regards,
Thomas
On Tue, Sep 30, 2008 at 12:02 AM, Warner Onstine <wo...@vmsinfo.com> wrote:
> Wow, after a long wait, it finally showed up (after like 5 - 10 minutes or
> more). Is there a config setting for this? I found the syncDelay, but I'm
> not sure if this is the issue as it does detect the change (I'm attributing
> this to the log files below) so I'm not sure what else I need to be doing
> here.
>
> Thanks!
>
> -warner
>
> On Sep 29, 2008, at 2:22 PM, Warner Onstine wrote:
>
>> More weirdness, I rebooted both machines and now all the content I pushed
>> up to node 2 just disappeared. Only the stuff from node 1 still exists.
>>
>> -warner
>>
>> On Sep 29, 2008, at 2:13 PM, Warner Onstine wrote:
>>
>>> I really am not sure what is going on here as things appear to be working
>>> (according to the logs), but unfortunately I can't see stuff from one node
>>> to a different node.
>>>
>>> I have two machines setup, each with their own nodes. They are both
>>> connecting to the same db, and when I fired up the second node everything
>>> seemed fine as the second node synced up with the first one.
>>>
>>> I then decided to mount this node (2) (I'm using WebDAV for my interface
>>> so I'm mounting it that way). I pushed up some new files and in the log
>>> files of both nodes I can see them syncing with each other.
>>>
>>> Node 2:
>>> 2008-09-29 17:03:18,200 INFO [ClusterNode] Appended revision: 1918
>>> 2008-09-29 17:03:18,592 INFO [ClusterNode] Appended revision: 1919
>>> 2008-09-29 17:03:18,939 INFO [ClusterNode] Appended revision: 1920
>>> 2008-09-29 17:03:23,230 INFO [ClusterNode] Appended revision: 1923
>>> 2008-09-29 17:03:23,681 INFO [ClusterNode] Appended revision: 1924
>>> 2008-09-29 17:03:24,017 INFO [ClusterNode] Appended revision: 1925
>>>
>>>
>>> Node 1:
>>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
>>> '1917' created by this journal, skipped.
>>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
>>> '1918' created by this journal, skipped.
>>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
>>> '1919' created by this journal, skipped.
>>> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
>>> '1920' created by this journal, skipped.
>>> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
>>> '1921' created by this journal, skipped.
>>> 2008-09-29 17:03:22,466 INFO [AbstractJournal] Synchronized to revision:
>>> 1921
>>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
>>> '1922' created by this journal, skipped.
>>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
>>> '1923' created by this journal, skipped.
>>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
>>> '1924' created by this journal, skipped.
>>> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
>>> '1925' created by this journal, skipped.
>>> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
>>> '1926' created by this journal, skipped.
>>> 2008-09-29 17:03:27,473 INFO [AbstractJournal] Synchronized to revision:
>>> 1926
>>>
>>> But when I look at these two nodes separately one has the new content and
>>> one doesn't. Curious, I added new content to node 1 and the same behavior
>>> comes up where I can see the new content I just put up on node 1, but not on
>>> node 2.
>>>
>>> Any ideas? This seems to be very odd behavior and I'm not sure if it has
>>> something to do with WebDAV or not.
>>>
>>> -warner
>>
>
>
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
Wow, after a long wait, it finally showed up (after like 5 - 10
minutes or more). Is there a config setting for this? I found the
syncDelay, but I'm not sure if this is the issue as it does detect the
change (I'm attributing this to the log files below) so I'm not sure
what else I need to be doing here.
Thanks!
-warner
On Sep 29, 2008, at 2:22 PM, Warner Onstine wrote:
> More weirdness, I rebooted both machines and now all the content I
> pushed up to node 2 just disappeared. Only the stuff from node 1
> still exists.
>
> -warner
>
> On Sep 29, 2008, at 2:13 PM, Warner Onstine wrote:
>
>> I really am not sure what is going on here as things appear to be
>> working (according to the logs), but unfortunately I can't see
>> stuff from one node to a different node.
>>
>> I have two machines setup, each with their own nodes. They are both
>> connecting to the same db, and when I fired up the second node
>> everything seemed fine as the second node synced up with the first
>> one.
>>
>> I then decided to mount this node (2) (I'm using WebDAV for my
>> interface so I'm mounting it that way). I pushed up some new files
>> and in the log files of both nodes I can see them syncing with each
>> other.
>>
>> Node 2:
>> 2008-09-29 17:03:18,200 INFO [ClusterNode] Appended revision: 1918
>> 2008-09-29 17:03:18,592 INFO [ClusterNode] Appended revision: 1919
>> 2008-09-29 17:03:18,939 INFO [ClusterNode] Appended revision: 1920
>> 2008-09-29 17:03:23,230 INFO [ClusterNode] Appended revision: 1923
>> 2008-09-29 17:03:23,681 INFO [ClusterNode] Appended revision: 1924
>> 2008-09-29 17:03:24,017 INFO [ClusterNode] Appended revision: 1925
>>
>>
>> Node 1:
>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with
>> revision '1917' created by this journal, skipped.
>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with
>> revision '1918' created by this journal, skipped.
>> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with
>> revision '1919' created by this journal, skipped.
>> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with
>> revision '1920' created by this journal, skipped.
>> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with
>> revision '1921' created by this journal, skipped.
>> 2008-09-29 17:03:22,466 INFO [AbstractJournal] Synchronized to
>> revision: 1921
>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with
>> revision '1922' created by this journal, skipped.
>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with
>> revision '1923' created by this journal, skipped.
>> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with
>> revision '1924' created by this journal, skipped.
>> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with
>> revision '1925' created by this journal, skipped.
>> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with
>> revision '1926' created by this journal, skipped.
>> 2008-09-29 17:03:27,473 INFO [AbstractJournal] Synchronized to
>> revision: 1926
>>
>> But when I look at these two nodes separately one has the new
>> content and one doesn't. Curious, I added new content to node 1 and
>> the same behavior comes up where I can see the new content I just
>> put up on node 1, but not on node 2.
>>
>> Any ideas? This seems to be very odd behavior and I'm not sure if
>> it has something to do with WebDAV or not.
>>
>> -warner
>
Re: clustering doesn't appear to be
Posted by Warner Onstine <wo...@vmsinfo.com>.
More weirdness, I rebooted both machines and now all the content I
pushed up to node 2 just disappeared. Only the stuff from node 1 still
exists.
-warner
On Sep 29, 2008, at 2:13 PM, Warner Onstine wrote:
> I really am not sure what is going on here as things appear to be
> working (according to the logs), but unfortunately I can't see stuff
> from one node to a different node.
>
> I have two machines setup, each with their own nodes. They are both
> connecting to the same db, and when I fired up the second node
> everything seemed fine as the second node synced up with the first
> one.
>
> I then decided to mount this node (2) (I'm using WebDAV for my
> interface so I'm mounting it that way). I pushed up some new files
> and in the log files of both nodes I can see them syncing with each
> other.
>
> Node 2:
> 2008-09-29 17:03:18,200 INFO [ClusterNode] Appended revision: 1918
> 2008-09-29 17:03:18,592 INFO [ClusterNode] Appended revision: 1919
> 2008-09-29 17:03:18,939 INFO [ClusterNode] Appended revision: 1920
> 2008-09-29 17:03:23,230 INFO [ClusterNode] Appended revision: 1923
> 2008-09-29 17:03:23,681 INFO [ClusterNode] Appended revision: 1924
> 2008-09-29 17:03:24,017 INFO [ClusterNode] Appended revision: 1925
>
>
> Node 1:
> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
> '1917' created by this journal, skipped.
> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
> '1918' created by this journal, skipped.
> 2008-09-29 17:03:22,464 INFO [AbstractJournal] Record with revision
> '1919' created by this journal, skipped.
> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
> '1920' created by this journal, skipped.
> 2008-09-29 17:03:22,465 INFO [AbstractJournal] Record with revision
> '1921' created by this journal, skipped.
> 2008-09-29 17:03:22,466 INFO [AbstractJournal] Synchronized to
> revision: 1921
> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
> '1922' created by this journal, skipped.
> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
> '1923' created by this journal, skipped.
> 2008-09-29 17:03:27,471 INFO [AbstractJournal] Record with revision
> '1924' created by this journal, skipped.
> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
> '1925' created by this journal, skipped.
> 2008-09-29 17:03:27,472 INFO [AbstractJournal] Record with revision
> '1926' created by this journal, skipped.
> 2008-09-29 17:03:27,473 INFO [AbstractJournal] Synchronized to
> revision: 1926
>
> But when I look at these two nodes separately one has the new
> content and one doesn't. Curious, I added new content to node 1 and
> the same behavior comes up where I can see the new content I just
> put up on node 1, but not on node 2.
>
> Any ideas? This seems to be very odd behavior and I'm not sure if it
> has something to do with WebDAV or not.
>
> -warner