You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2013/02/10 20:01:25 UTC
[VOTE] Release Apache ManifoldCF 1.1.1, RC0
Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
The release artifact can be downloaded from:
http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
There is a tag at:
https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
This release has been made primarily to fix a leak of connection
handles, described by CONNECTORS-638. Other major fixes have also
been included, specifically:
- Fix the maven build (various tickets)
- Fix the rather broken Elastic Search connector (also various tickets)
Karl
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Piergiorgio Lucidi <pi...@apache.org>.
- checked signatures
- ran all tests using Maven
- crawled using CMIS
+1 from me
Piergiorgio
2013/2/10 Karl Wright <da...@gmail.com>
> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>
> The release artifact can be downloaded from:
>
> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>
> There is a tag at:
>
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>
> This release has been made primarily to fix a leak of connection
> handles, described by CONNECTORS-638. Other major fixes have also
> been included, specifically:
>
> - Fix the maven build (various tickets)
> - Fix the rather broken Elastic Search connector (also various tickets)
>
> Karl
>
> --
> Piergiorgio Lucidi
> http://www.open4dev.com
[RESULT][VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
Five +1's, no 0's, and only one (retracted) -1. ;-)
Vote passes.
Karl
On Wed, Feb 13, 2013 at 10:29 AM, Maciej Liżewski
<ma...@gmail.com> wrote:
> then I am ok with releasing the patch.
>
>
> 2013/2/13 Karl Wright <da...@gmail.com>
>
>> The forced metadata addition is not in 1.1.1 at all; it's a 1.2
>> feature. So there is no point in pulling up a fix for a non-existent
>> feature.
>>
>> Karl
>>
>> On Wed, Feb 13, 2013 at 8:30 AM, Maciej Liżewski
>> <ma...@gmail.com> wrote:
>> > if it is still possible - I suggest to add patch for CONNECTORS-645 to
>> this
>> > release. it should be quite simple, but it causes NPE on document
>> deletion
>> > when forced metadata is used...
>> >
>> >
>> > 2013/2/12 Karl Wright <da...@gmail.com>
>> >
>> >> Right, since this is a long-standing problem and this is a patch
>> >> release, I'd hope that we could hold off until the next real release
>> >> for this one.
>> >>
>> >> I doubt it will be too challenging to fix.
>> >>
>> >> Karl
>> >>
>> >> On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <
>> e.f.garasen@usit.uio.no>
>> >> wrote:
>> >> >
>> >> > You are probably right. I can withdraw my vote, but I'm unsure
>> whether I
>> >> > should wait and see what happens with the crawl I just started on our
>> >> test
>> >> > server with new hop filter settings. I can then make a final vote
>> >> tomorrow.
>> >> > All the other tests I have done with this RC have passed.
>> >> >
>> >> > Erlend
>> >> >
>> >> >
>> >> > On 12.02.13 19.06, Karl Wright wrote:
>> >> >>
>> >> >> If this problem is non-critical, and has been around a long time, it
>> >> >> is not necessary to cancel a release in order to fix it. The logic
>> in
>> >> >> question has not changed since probably ManifoldCF 0.3 or so.
>> >> >>
>> >> >> Karl
>> >> >>
>> >> >> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <
>> >> e.f.garasen@usit.uio.no>
>> >> >> wrote:
>> >> >>>
>> >> >>>
>> >> >>> -1 due to CONNECTORS-644.
>> >> >>>
>> >> >>> The job restart link does not work, causing Error: Repeated service
>> >> >>> interruptions - failure getting document version. I think this
>> >> >>> functionality
>> >> >>> is so basic, so I think it should be solved for this release.
>> >> >>>
>> >> >>> This problem is totally unrelated to Resin. It happens if you are
>> >> running
>> >> >>> Jetty as well.
>> >> >>>
>> >> >>>
>> >> >>> Erlend
>> >> >>>
>> >> >>> On 10.02.13 20.01, Karl Wright wrote:
>> >> >>>>
>> >> >>>>
>> >> >>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>> >> >>>>
>> >> >>>> The release artifact can be downloaded from:
>> >> >>>>
>> >> >>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>> >> >>>>
>> >> >>>> There is a tag at:
>> >> >>>>
>> >> >>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>> >> >>>>
>> >> >>>> This release has been made primarily to fix a leak of connection
>> >> >>>> handles, described by CONNECTORS-638. Other major fixes have also
>> >> >>>> been included, specifically:
>> >> >>>>
>> >> >>>> - Fix the maven build (various tickets)
>> >> >>>> - Fix the rather broken Elastic Search connector (also various
>> >> tickets)
>> >> >>>>
>> >> >>>> Karl
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Erlend Garåsen
>> >> >>> Center for Information Technology Services
>> >> >>> University of Oslo
>> >> >>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> >> >>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968,
>> VIP:
>> >> >>> 31050
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Erlend Garåsen
>> >> > Center for Information Technology Services
>> >> > University of Oslo
>> >> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> >> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>> >> 31050
>> >>
>>
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Maciej Liżewski <ma...@gmail.com>.
then I am ok with releasing the patch.
2013/2/13 Karl Wright <da...@gmail.com>
> The forced metadata addition is not in 1.1.1 at all; it's a 1.2
> feature. So there is no point in pulling up a fix for a non-existent
> feature.
>
> Karl
>
> On Wed, Feb 13, 2013 at 8:30 AM, Maciej Liżewski
> <ma...@gmail.com> wrote:
> > if it is still possible - I suggest to add patch for CONNECTORS-645 to
> this
> > release. it should be quite simple, but it causes NPE on document
> deletion
> > when forced metadata is used...
> >
> >
> > 2013/2/12 Karl Wright <da...@gmail.com>
> >
> >> Right, since this is a long-standing problem and this is a patch
> >> release, I'd hope that we could hold off until the next real release
> >> for this one.
> >>
> >> I doubt it will be too challenging to fix.
> >>
> >> Karl
> >>
> >> On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <
> e.f.garasen@usit.uio.no>
> >> wrote:
> >> >
> >> > You are probably right. I can withdraw my vote, but I'm unsure
> whether I
> >> > should wait and see what happens with the crawl I just started on our
> >> test
> >> > server with new hop filter settings. I can then make a final vote
> >> tomorrow.
> >> > All the other tests I have done with this RC have passed.
> >> >
> >> > Erlend
> >> >
> >> >
> >> > On 12.02.13 19.06, Karl Wright wrote:
> >> >>
> >> >> If this problem is non-critical, and has been around a long time, it
> >> >> is not necessary to cancel a release in order to fix it. The logic
> in
> >> >> question has not changed since probably ManifoldCF 0.3 or so.
> >> >>
> >> >> Karl
> >> >>
> >> >> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <
> >> e.f.garasen@usit.uio.no>
> >> >> wrote:
> >> >>>
> >> >>>
> >> >>> -1 due to CONNECTORS-644.
> >> >>>
> >> >>> The job restart link does not work, causing Error: Repeated service
> >> >>> interruptions - failure getting document version. I think this
> >> >>> functionality
> >> >>> is so basic, so I think it should be solved for this release.
> >> >>>
> >> >>> This problem is totally unrelated to Resin. It happens if you are
> >> running
> >> >>> Jetty as well.
> >> >>>
> >> >>>
> >> >>> Erlend
> >> >>>
> >> >>> On 10.02.13 20.01, Karl Wright wrote:
> >> >>>>
> >> >>>>
> >> >>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
> >> >>>>
> >> >>>> The release artifact can be downloaded from:
> >> >>>>
> >> >>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
> >> >>>>
> >> >>>> There is a tag at:
> >> >>>>
> >> >>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
> >> >>>>
> >> >>>> This release has been made primarily to fix a leak of connection
> >> >>>> handles, described by CONNECTORS-638. Other major fixes have also
> >> >>>> been included, specifically:
> >> >>>>
> >> >>>> - Fix the maven build (various tickets)
> >> >>>> - Fix the rather broken Elastic Search connector (also various
> >> tickets)
> >> >>>>
> >> >>>> Karl
> >> >>>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Erlend Garåsen
> >> >>> Center for Information Technology Services
> >> >>> University of Oslo
> >> >>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> >> >>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968,
> VIP:
> >> >>> 31050
> >> >
> >> >
> >> >
> >> > --
> >> > Erlend Garåsen
> >> > Center for Information Technology Services
> >> > University of Oslo
> >> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> >> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
> >> 31050
> >>
>
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
The forced metadata addition is not in 1.1.1 at all; it's a 1.2
feature. So there is no point in pulling up a fix for a non-existent
feature.
Karl
On Wed, Feb 13, 2013 at 8:30 AM, Maciej Liżewski
<ma...@gmail.com> wrote:
> if it is still possible - I suggest to add patch for CONNECTORS-645 to this
> release. it should be quite simple, but it causes NPE on document deletion
> when forced metadata is used...
>
>
> 2013/2/12 Karl Wright <da...@gmail.com>
>
>> Right, since this is a long-standing problem and this is a patch
>> release, I'd hope that we could hold off until the next real release
>> for this one.
>>
>> I doubt it will be too challenging to fix.
>>
>> Karl
>>
>> On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <e....@usit.uio.no>
>> wrote:
>> >
>> > You are probably right. I can withdraw my vote, but I'm unsure whether I
>> > should wait and see what happens with the crawl I just started on our
>> test
>> > server with new hop filter settings. I can then make a final vote
>> tomorrow.
>> > All the other tests I have done with this RC have passed.
>> >
>> > Erlend
>> >
>> >
>> > On 12.02.13 19.06, Karl Wright wrote:
>> >>
>> >> If this problem is non-critical, and has been around a long time, it
>> >> is not necessary to cancel a release in order to fix it. The logic in
>> >> question has not changed since probably ManifoldCF 0.3 or so.
>> >>
>> >> Karl
>> >>
>> >> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <
>> e.f.garasen@usit.uio.no>
>> >> wrote:
>> >>>
>> >>>
>> >>> -1 due to CONNECTORS-644.
>> >>>
>> >>> The job restart link does not work, causing Error: Repeated service
>> >>> interruptions - failure getting document version. I think this
>> >>> functionality
>> >>> is so basic, so I think it should be solved for this release.
>> >>>
>> >>> This problem is totally unrelated to Resin. It happens if you are
>> running
>> >>> Jetty as well.
>> >>>
>> >>>
>> >>> Erlend
>> >>>
>> >>> On 10.02.13 20.01, Karl Wright wrote:
>> >>>>
>> >>>>
>> >>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>> >>>>
>> >>>> The release artifact can be downloaded from:
>> >>>>
>> >>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>> >>>>
>> >>>> There is a tag at:
>> >>>>
>> >>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>> >>>>
>> >>>> This release has been made primarily to fix a leak of connection
>> >>>> handles, described by CONNECTORS-638. Other major fixes have also
>> >>>> been included, specifically:
>> >>>>
>> >>>> - Fix the maven build (various tickets)
>> >>>> - Fix the rather broken Elastic Search connector (also various
>> tickets)
>> >>>>
>> >>>> Karl
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Erlend Garåsen
>> >>> Center for Information Technology Services
>> >>> University of Oslo
>> >>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> >>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>> >>> 31050
>> >
>> >
>> >
>> > --
>> > Erlend Garåsen
>> > Center for Information Technology Services
>> > University of Oslo
>> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>> 31050
>>
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Maciej Liżewski <ma...@gmail.com>.
if it is still possible - I suggest to add patch for CONNECTORS-645 to this
release. it should be quite simple, but it causes NPE on document deletion
when forced metadata is used...
2013/2/12 Karl Wright <da...@gmail.com>
> Right, since this is a long-standing problem and this is a patch
> release, I'd hope that we could hold off until the next real release
> for this one.
>
> I doubt it will be too challenging to fix.
>
> Karl
>
> On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <e....@usit.uio.no>
> wrote:
> >
> > You are probably right. I can withdraw my vote, but I'm unsure whether I
> > should wait and see what happens with the crawl I just started on our
> test
> > server with new hop filter settings. I can then make a final vote
> tomorrow.
> > All the other tests I have done with this RC have passed.
> >
> > Erlend
> >
> >
> > On 12.02.13 19.06, Karl Wright wrote:
> >>
> >> If this problem is non-critical, and has been around a long time, it
> >> is not necessary to cancel a release in order to fix it. The logic in
> >> question has not changed since probably ManifoldCF 0.3 or so.
> >>
> >> Karl
> >>
> >> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <
> e.f.garasen@usit.uio.no>
> >> wrote:
> >>>
> >>>
> >>> -1 due to CONNECTORS-644.
> >>>
> >>> The job restart link does not work, causing Error: Repeated service
> >>> interruptions - failure getting document version. I think this
> >>> functionality
> >>> is so basic, so I think it should be solved for this release.
> >>>
> >>> This problem is totally unrelated to Resin. It happens if you are
> running
> >>> Jetty as well.
> >>>
> >>>
> >>> Erlend
> >>>
> >>> On 10.02.13 20.01, Karl Wright wrote:
> >>>>
> >>>>
> >>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
> >>>>
> >>>> The release artifact can be downloaded from:
> >>>>
> >>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
> >>>>
> >>>> There is a tag at:
> >>>>
> >>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
> >>>>
> >>>> This release has been made primarily to fix a leak of connection
> >>>> handles, described by CONNECTORS-638. Other major fixes have also
> >>>> been included, specifically:
> >>>>
> >>>> - Fix the maven build (various tickets)
> >>>> - Fix the rather broken Elastic Search connector (also various
> tickets)
> >>>>
> >>>> Karl
> >>>>
> >>>
> >>>
> >>> --
> >>> Erlend Garåsen
> >>> Center for Information Technology Services
> >>> University of Oslo
> >>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> >>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
> >>> 31050
> >
> >
> >
> > --
> > Erlend Garåsen
> > Center for Information Technology Services
> > University of Oslo
> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
> 31050
>
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
+1 (I'm withdrawing my previous -1).
- Downloaded the binary zip version:
* It runs now stable on Resin, even after a test where I stopped the
running job and started it once again. Posting to Solr 4.0 works.
- Downloaded the source zip version:
* ran ant uitest
* ran Jetty within both the example and multithread-example folders
and posted to Solr 3.1 (backward compatibility test)
Erlend
On 12.02.13 20.39, Karl Wright wrote:
> Right, since this is a long-standing problem and this is a patch
> release, I'd hope that we could hold off until the next real release
> for this one.
>
> I doubt it will be too challenging to fix.
>
> Karl
>
> On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <e....@usit.uio.no> wrote:
>>
>> You are probably right. I can withdraw my vote, but I'm unsure whether I
>> should wait and see what happens with the crawl I just started on our test
>> server with new hop filter settings. I can then make a final vote tomorrow.
>> All the other tests I have done with this RC have passed.
>>
>> Erlend
>>
>>
>> On 12.02.13 19.06, Karl Wright wrote:
>>>
>>> If this problem is non-critical, and has been around a long time, it
>>> is not necessary to cancel a release in order to fix it. The logic in
>>> question has not changed since probably ManifoldCF 0.3 or so.
>>>
>>> Karl
>>>
>>> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <e....@usit.uio.no>
>>> wrote:
>>>>
>>>>
>>>> -1 due to CONNECTORS-644.
>>>>
>>>> The job restart link does not work, causing Error: Repeated service
>>>> interruptions - failure getting document version. I think this
>>>> functionality
>>>> is so basic, so I think it should be solved for this release.
>>>>
>>>> This problem is totally unrelated to Resin. It happens if you are running
>>>> Jetty as well.
>>>>
>>>>
>>>> Erlend
>>>>
>>>> On 10.02.13 20.01, Karl Wright wrote:
>>>>>
>>>>>
>>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>>>
>>>>> The release artifact can be downloaded from:
>>>>>
>>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>>>
>>>>> There is a tag at:
>>>>>
>>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>>>
>>>>> This release has been made primarily to fix a leak of connection
>>>>> handles, described by CONNECTORS-638. Other major fixes have also
>>>>> been included, specifically:
>>>>>
>>>>> - Fix the maven build (various tickets)
>>>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>>>
>>>>> Karl
>>>>>
>>>>
>>>>
>>>> --
>>>> Erlend Garåsen
>>>> Center for Information Technology Services
>>>> University of Oslo
>>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>>>> 31050
>>
>>
>>
>> --
>> Erlend Garåsen
>> Center for Information Technology Services
>> University of Oslo
>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
Right, since this is a long-standing problem and this is a patch
release, I'd hope that we could hold off until the next real release
for this one.
I doubt it will be too challenging to fix.
Karl
On Tue, Feb 12, 2013 at 1:22 PM, Erlend Garåsen <e....@usit.uio.no> wrote:
>
> You are probably right. I can withdraw my vote, but I'm unsure whether I
> should wait and see what happens with the crawl I just started on our test
> server with new hop filter settings. I can then make a final vote tomorrow.
> All the other tests I have done with this RC have passed.
>
> Erlend
>
>
> On 12.02.13 19.06, Karl Wright wrote:
>>
>> If this problem is non-critical, and has been around a long time, it
>> is not necessary to cancel a release in order to fix it. The logic in
>> question has not changed since probably ManifoldCF 0.3 or so.
>>
>> Karl
>>
>> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <e....@usit.uio.no>
>> wrote:
>>>
>>>
>>> -1 due to CONNECTORS-644.
>>>
>>> The job restart link does not work, causing Error: Repeated service
>>> interruptions - failure getting document version. I think this
>>> functionality
>>> is so basic, so I think it should be solved for this release.
>>>
>>> This problem is totally unrelated to Resin. It happens if you are running
>>> Jetty as well.
>>>
>>>
>>> Erlend
>>>
>>> On 10.02.13 20.01, Karl Wright wrote:
>>>>
>>>>
>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>>
>>>> The release artifact can be downloaded from:
>>>>
>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>>
>>>> There is a tag at:
>>>>
>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>>
>>>> This release has been made primarily to fix a leak of connection
>>>> handles, described by CONNECTORS-638. Other major fixes have also
>>>> been included, specifically:
>>>>
>>>> - Fix the maven build (various tickets)
>>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>>
>>>> Karl
>>>>
>>>
>>>
>>> --
>>> Erlend Garåsen
>>> Center for Information Technology Services
>>> University of Oslo
>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>>> 31050
>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
You are probably right. I can withdraw my vote, but I'm unsure whether I
should wait and see what happens with the crawl I just started on our
test server with new hop filter settings. I can then make a final vote
tomorrow. All the other tests I have done with this RC have passed.
Erlend
On 12.02.13 19.06, Karl Wright wrote:
> If this problem is non-critical, and has been around a long time, it
> is not necessary to cancel a release in order to fix it. The logic in
> question has not changed since probably ManifoldCF 0.3 or so.
>
> Karl
>
> On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <e....@usit.uio.no> wrote:
>>
>> -1 due to CONNECTORS-644.
>>
>> The job restart link does not work, causing Error: Repeated service
>> interruptions - failure getting document version. I think this functionality
>> is so basic, so I think it should be solved for this release.
>>
>> This problem is totally unrelated to Resin. It happens if you are running
>> Jetty as well.
>>
>>
>> Erlend
>>
>> On 10.02.13 20.01, Karl Wright wrote:
>>>
>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>
>>> The release artifact can be downloaded from:
>>>
>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>
>>> There is a tag at:
>>>
>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>
>>> This release has been made primarily to fix a leak of connection
>>> handles, described by CONNECTORS-638. Other major fixes have also
>>> been included, specifically:
>>>
>>> - Fix the maven build (various tickets)
>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>
>>> Karl
>>>
>>
>>
>> --
>> Erlend Garåsen
>> Center for Information Technology Services
>> University of Oslo
>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
If this problem is non-critical, and has been around a long time, it
is not necessary to cancel a release in order to fix it. The logic in
question has not changed since probably ManifoldCF 0.3 or so.
Karl
On Tue, Feb 12, 2013 at 1:04 PM, Erlend Garåsen <e....@usit.uio.no> wrote:
>
> -1 due to CONNECTORS-644.
>
> The job restart link does not work, causing Error: Repeated service
> interruptions - failure getting document version. I think this functionality
> is so basic, so I think it should be solved for this release.
>
> This problem is totally unrelated to Resin. It happens if you are running
> Jetty as well.
>
>
> Erlend
>
> On 10.02.13 20.01, Karl Wright wrote:
>>
>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>
>> The release artifact can be downloaded from:
>>
>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>
>> There is a tag at:
>>
>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>
>> This release has been made primarily to fix a leak of connection
>> handles, described by CONNECTORS-638. Other major fixes have also
>> been included, specifically:
>>
>> - Fix the maven build (various tickets)
>> - Fix the rather broken Elastic Search connector (also various tickets)
>>
>> Karl
>>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
-1 due to CONNECTORS-644.
The job restart link does not work, causing Error: Repeated service
interruptions - failure getting document version. I think this
functionality is so basic, so I think it should be solved for this release.
This problem is totally unrelated to Resin. It happens if you are
running Jetty as well.
Erlend
On 10.02.13 20.01, Karl Wright wrote:
> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>
> The release artifact can be downloaded from:
>
> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>
> There is a tag at:
>
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>
> This release has been made primarily to fix a leak of connection
> handles, described by CONNECTORS-638. Other major fixes have also
> been included, specifically:
>
> - Fix the maven build (various tickets)
> - Fix the rather broken Elastic Search connector (also various tickets)
>
> Karl
>
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
Passes all tests.
+1 from me.
Karl
On Sun, Feb 10, 2013 at 2:01 PM, Karl Wright <da...@gmail.com> wrote:
> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>
> The release artifact can be downloaded from:
>
> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>
> There is a tag at:
>
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>
> This release has been made primarily to fix a leak of connection
> handles, described by CONNECTORS-638. Other major fixes have also
> been included, specifically:
>
> - Fix the maven build (various tickets)
> - Fix the rather broken Elastic Search connector (also various tickets)
>
> Karl
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Maciej Liżewski <ma...@gmail.com>.
build everything with maven,
run all tests,
tried to run jetty-runner with maven
everything is running ok.
+1 for the release from me
2013/2/12 Karl Wright <da...@gmail.com>
> Hmm, I haven't tried the restart functionality in ages. But if there
> is a failure, obviously restart won't work, because the job will
> terminate first.
>
> Can you look at simple history and tell us whether the fetches succeed
> or fail? If they fail, and get retried, then that is interesting and
> you should look there. If the failure is because it can't get the
> documents into Solr, then the fetches will be retried too, and you
> will see errors on the solr indexing attempts.
>
> Karl
>
> On Tue, Feb 12, 2013 at 8:23 AM, Erlend Garåsen <e....@usit.uio.no>
> wrote:
> >
> > I tried to restart the crawl ten minutes after I started it. The job ends
> > after a while and will not start again. This is the status after it
> stopped:
> > Error: Repeated service interruptions - failure getting document version
> >
> > If I start it manually, it just fetches and fetches without posting
> anything
> > to Solr.
> >
> > The only thing I did while it was running the first time was to edit the
> > exclude list once - removed a white space at the end of a reg exp rule.
> >
> > Then I commented out the regexp line in case it DID affected the
> documents
> > (it shouldn't) and restarted again. Same problem - the job does not want
> to
> > start: Error: Repeated service interruptions - failure getting document
> > version
> >
> > Just before the job ends, the result description shows "Interrupted: Job
> no
> > longer active". This is normal, but why won't MCF start the job again
> after
> > it stops?
> >
> > Same problem after I manually starts it - MCF just fetches and fetches
> > without posting anything to Solr.
> >
> > E
> >
> >
> > On 12.02.13 13.38, Erlend Garåsen wrote:
> >>
> >>
> >> I have changed some settings in MCF which will reduce the heavy load on
> >> our PG server (changed hop count mode to "Keep unreachable documents,
> >> forever").
> >>
> >> I will start a new crawl today and make a final vote tomorrow.
> >>
> >> Erlend
> >>
> >> On 11.02.13 20.49, Karl Wright wrote:
> >>>
> >>> I've looked at this enough now to conclude that this problem is
> >>> probably not intrinsic to ManifoldCF. It may instead be due to
> >>> timeouts present in Erlend's PostgreSQL installation. I am therefore
> >>> leaving the vote open until there is some reason to believe that there
> >>> is a general problem here.
> >>>
> >>> Thanks,
> >>> Karl
> >>>
> >>>
> >>> On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
> >>> <e....@usit.uio.no> wrote:
> >>>>
> >>>>
> >>>> The job just stopped working and nothing suspicious in my logs. The
> >>>> database
> >>>> people are saying that we have connection locks again ("<idle> in
> >>>> transaction").
> >>>>
> >>>> Karl, you mentioned that in order to use the following parameter:
> >>>> <property name="org.apache.manifoldcf.database.connectiontracking"
> >>>> value="true"/>
> >>>> there was no way back to use an older release due to changes in the
> >>>> database. That's ok, but was that just a temporary functionality,
> which
> >>>> means, I need to clear my database in order to use 1.1.1 RC0?
> >>>>
> >>>> Erlend
> >>>>
> >>>>
> >>>> On 10.02.13 20.01, Karl Wright wrote:
> >>>>>
> >>>>>
> >>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
> >>>>>
> >>>>> The release artifact can be downloaded from:
> >>>>>
> >>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
> >>>>>
> >>>>> There is a tag at:
> >>>>>
> >>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
> >>>>>
> >>>>> This release has been made primarily to fix a leak of connection
> >>>>> handles, described by CONNECTORS-638. Other major fixes have also
> >>>>> been included, specifically:
> >>>>>
> >>>>> - Fix the maven build (various tickets)
> >>>>> - Fix the rather broken Elastic Search connector (also various
> tickets)
> >>>>>
> >>>>> Karl
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Erlend Garåsen
> >>>> Center for Information Technology Services
> >>>> University of Oslo
> >>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> >>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
> >>>> 31050
> >>
> >>
> >>
> >
> >
> > --
> > Erlend Garåsen
> > Center for Information Technology Services
> > University of Oslo
> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
> 31050
>
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
Hmm, I haven't tried the restart functionality in ages. But if there
is a failure, obviously restart won't work, because the job will
terminate first.
Can you look at simple history and tell us whether the fetches succeed
or fail? If they fail, and get retried, then that is interesting and
you should look there. If the failure is because it can't get the
documents into Solr, then the fetches will be retried too, and you
will see errors on the solr indexing attempts.
Karl
On Tue, Feb 12, 2013 at 8:23 AM, Erlend Garåsen <e....@usit.uio.no> wrote:
>
> I tried to restart the crawl ten minutes after I started it. The job ends
> after a while and will not start again. This is the status after it stopped:
> Error: Repeated service interruptions - failure getting document version
>
> If I start it manually, it just fetches and fetches without posting anything
> to Solr.
>
> The only thing I did while it was running the first time was to edit the
> exclude list once - removed a white space at the end of a reg exp rule.
>
> Then I commented out the regexp line in case it DID affected the documents
> (it shouldn't) and restarted again. Same problem - the job does not want to
> start: Error: Repeated service interruptions - failure getting document
> version
>
> Just before the job ends, the result description shows "Interrupted: Job no
> longer active". This is normal, but why won't MCF start the job again after
> it stops?
>
> Same problem after I manually starts it - MCF just fetches and fetches
> without posting anything to Solr.
>
> E
>
>
> On 12.02.13 13.38, Erlend Garåsen wrote:
>>
>>
>> I have changed some settings in MCF which will reduce the heavy load on
>> our PG server (changed hop count mode to "Keep unreachable documents,
>> forever").
>>
>> I will start a new crawl today and make a final vote tomorrow.
>>
>> Erlend
>>
>> On 11.02.13 20.49, Karl Wright wrote:
>>>
>>> I've looked at this enough now to conclude that this problem is
>>> probably not intrinsic to ManifoldCF. It may instead be due to
>>> timeouts present in Erlend's PostgreSQL installation. I am therefore
>>> leaving the vote open until there is some reason to believe that there
>>> is a general problem here.
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>> On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
>>> <e....@usit.uio.no> wrote:
>>>>
>>>>
>>>> The job just stopped working and nothing suspicious in my logs. The
>>>> database
>>>> people are saying that we have connection locks again ("<idle> in
>>>> transaction").
>>>>
>>>> Karl, you mentioned that in order to use the following parameter:
>>>> <property name="org.apache.manifoldcf.database.connectiontracking"
>>>> value="true"/>
>>>> there was no way back to use an older release due to changes in the
>>>> database. That's ok, but was that just a temporary functionality, which
>>>> means, I need to clear my database in order to use 1.1.1 RC0?
>>>>
>>>> Erlend
>>>>
>>>>
>>>> On 10.02.13 20.01, Karl Wright wrote:
>>>>>
>>>>>
>>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>>>
>>>>> The release artifact can be downloaded from:
>>>>>
>>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>>>
>>>>> There is a tag at:
>>>>>
>>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>>>
>>>>> This release has been made primarily to fix a leak of connection
>>>>> handles, described by CONNECTORS-638. Other major fixes have also
>>>>> been included, specifically:
>>>>>
>>>>> - Fix the maven build (various tickets)
>>>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>>>
>>>>> Karl
>>>>>
>>>>
>>>>
>>>> --
>>>> Erlend Garåsen
>>>> Center for Information Technology Services
>>>> University of Oslo
>>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>>>> 31050
>>
>>
>>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
I tried to restart the crawl ten minutes after I started it. The job
ends after a while and will not start again. This is the status after it
stopped:
Error: Repeated service interruptions - failure getting document version
If I start it manually, it just fetches and fetches without posting
anything to Solr.
The only thing I did while it was running the first time was to edit the
exclude list once - removed a white space at the end of a reg exp rule.
Then I commented out the regexp line in case it DID affected the
documents (it shouldn't) and restarted again. Same problem - the job
does not want to start: Error: Repeated service interruptions - failure
getting document version
Just before the job ends, the result description shows "Interrupted: Job
no longer active". This is normal, but why won't MCF start the job again
after it stops?
Same problem after I manually starts it - MCF just fetches and fetches
without posting anything to Solr.
E
On 12.02.13 13.38, Erlend Garåsen wrote:
>
> I have changed some settings in MCF which will reduce the heavy load on
> our PG server (changed hop count mode to "Keep unreachable documents,
> forever").
>
> I will start a new crawl today and make a final vote tomorrow.
>
> Erlend
>
> On 11.02.13 20.49, Karl Wright wrote:
>> I've looked at this enough now to conclude that this problem is
>> probably not intrinsic to ManifoldCF. It may instead be due to
>> timeouts present in Erlend's PostgreSQL installation. I am therefore
>> leaving the vote open until there is some reason to believe that there
>> is a general problem here.
>>
>> Thanks,
>> Karl
>>
>>
>> On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
>> <e....@usit.uio.no> wrote:
>>>
>>> The job just stopped working and nothing suspicious in my logs. The
>>> database
>>> people are saying that we have connection locks again ("<idle> in
>>> transaction").
>>>
>>> Karl, you mentioned that in order to use the following parameter:
>>> <property name="org.apache.manifoldcf.database.connectiontracking"
>>> value="true"/>
>>> there was no way back to use an older release due to changes in the
>>> database. That's ok, but was that just a temporary functionality, which
>>> means, I need to clear my database in order to use 1.1.1 RC0?
>>>
>>> Erlend
>>>
>>>
>>> On 10.02.13 20.01, Karl Wright wrote:
>>>>
>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>>
>>>> The release artifact can be downloaded from:
>>>>
>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>>
>>>> There is a tag at:
>>>>
>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>>
>>>> This release has been made primarily to fix a leak of connection
>>>> handles, described by CONNECTORS-638. Other major fixes have also
>>>> been included, specifically:
>>>>
>>>> - Fix the maven build (various tickets)
>>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>>
>>>> Karl
>>>>
>>>
>>>
>>> --
>>> Erlend Garåsen
>>> Center for Information Technology Services
>>> University of Oslo
>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP:
>>> 31050
>
>
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
I have changed some settings in MCF which will reduce the heavy load on
our PG server (changed hop count mode to "Keep unreachable documents,
forever").
I will start a new crawl today and make a final vote tomorrow.
Erlend
On 11.02.13 20.49, Karl Wright wrote:
> I've looked at this enough now to conclude that this problem is
> probably not intrinsic to ManifoldCF. It may instead be due to
> timeouts present in Erlend's PostgreSQL installation. I am therefore
> leaving the vote open until there is some reason to believe that there
> is a general problem here.
>
> Thanks,
> Karl
>
>
> On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
> <e....@usit.uio.no> wrote:
>>
>> The job just stopped working and nothing suspicious in my logs. The database
>> people are saying that we have connection locks again ("<idle> in
>> transaction").
>>
>> Karl, you mentioned that in order to use the following parameter:
>> <property name="org.apache.manifoldcf.database.connectiontracking"
>> value="true"/>
>> there was no way back to use an older release due to changes in the
>> database. That's ok, but was that just a temporary functionality, which
>> means, I need to clear my database in order to use 1.1.1 RC0?
>>
>> Erlend
>>
>>
>> On 10.02.13 20.01, Karl Wright wrote:
>>>
>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>>
>>> The release artifact can be downloaded from:
>>>
>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>>
>>> There is a tag at:
>>>
>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>>
>>> This release has been made primarily to fix a leak of connection
>>> handles, described by CONNECTORS-638. Other major fixes have also
>>> been included, specifically:
>>>
>>> - Fix the maven build (various tickets)
>>> - Fix the rather broken Elastic Search connector (also various tickets)
>>>
>>> Karl
>>>
>>
>>
>> --
>> Erlend Garåsen
>> Center for Information Technology Services
>> University of Oslo
>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
I've looked at this enough now to conclude that this problem is
probably not intrinsic to ManifoldCF. It may instead be due to
timeouts present in Erlend's PostgreSQL installation. I am therefore
leaving the vote open until there is some reason to believe that there
is a general problem here.
Thanks,
Karl
On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
<e....@usit.uio.no> wrote:
>
> The job just stopped working and nothing suspicious in my logs. The database
> people are saying that we have connection locks again ("<idle> in
> transaction").
>
> Karl, you mentioned that in order to use the following parameter:
> <property name="org.apache.manifoldcf.database.connectiontracking"
> value="true"/>
> there was no way back to use an older release due to changes in the
> database. That's ok, but was that just a temporary functionality, which
> means, I need to clear my database in order to use 1.1.1 RC0?
>
> Erlend
>
>
> On 10.02.13 20.01, Karl Wright wrote:
>>
>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>
>> The release artifact can be downloaded from:
>>
>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>
>> There is a tag at:
>>
>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>
>> This release has been made primarily to fix a leak of connection
>> handles, described by CONNECTORS-638. Other major fixes have also
>> been included, specifically:
>>
>> - Fix the maven build (various tickets)
>> - Fix the rather broken Elastic Search connector (also various tickets)
>>
>> Karl
>>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
On 11.02.13 17.50, Karl Wright wrote:
> The trace didn't look like it was the result of stuck ManifoldCF locks.
Even though it does not seem to be a result of this, I found an error in
our control script. The path to executecommand.sh was incorrect for the
"stop" function.
I'll send your suggestions to the PostgreSQL admins and try to get more
information.
Erlend
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
The trace didn't look like it was the result of stuck ManifoldCF locks.
Karl
On Mon, Feb 11, 2013 at 11:43 AM, Erlend Garåsen
<e....@usit.uio.no> wrote:
> On 11.02.13 17.14, Karl Wright wrote:
>>
>> I've confirmed that there's a deadlock of some kind; it's occurring as
>> a result of the hopcount depth tracking. The issue seems to be nested
>> transactions; PostgreSQL doesn't appear to be dealing with these
>> properly in all cases, and winds up getting a deadlock that it doesn't
>> detect.
>>
>> I have to look carefully at the code to see if it can be restructured.
>
>
> Perhaps I should wait till I start the job once again?
>
> When I had the last version from trunk deployed on our test version, the job
> ran for over three days without any problems. This deadlock occurred only
> one hour before I started he job earlier today with version 1.1.1 RC0
> installed. The only thing I did prior to the upgrade was to stop the running
> job, stopping the Agent process and the Resin instance. I _did_ notice that
> the Agent process was still running, so I killed it (-9) and cleaned locks
> thereafter. I doubt that this had some impact on PG, but I'm mentioning this
> anyway in order to provide as much information as possible. By looking bash
> history, I can confirm that I did everything in the correct order: killed
> the process and then ran the lock clean command class.
>
> Our agent control script is also attached in case we're doing something
> wrong.
>
>
> Erlend
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
On 11.02.13 17.14, Karl Wright wrote:
> I've confirmed that there's a deadlock of some kind; it's occurring as
> a result of the hopcount depth tracking. The issue seems to be nested
> transactions; PostgreSQL doesn't appear to be dealing with these
> properly in all cases, and winds up getting a deadlock that it doesn't
> detect.
>
> I have to look carefully at the code to see if it can be restructured.
Perhaps I should wait till I start the job once again?
When I had the last version from trunk deployed on our test version, the
job ran for over three days without any problems. This deadlock occurred
only one hour before I started he job earlier today with version 1.1.1
RC0 installed. The only thing I did prior to the upgrade was to stop the
running job, stopping the Agent process and the Resin instance. I _did_
notice that the Agent process was still running, so I killed it (-9) and
cleaned locks thereafter. I doubt that this had some impact on PG, but
I'm mentioning this anyway in order to provide as much information as
possible. By looking bash history, I can confirm that I did everything
in the correct order: killed the process and then ran the lock clean
command class.
Our agent control script is also attached in case we're doing something
wrong.
Erlend
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
I looked at the thread dump in more detail, and the situation is now less clear.
(1) I see no obvious ManifoldCF-mediated deadlock at all. Everything
looks as it should.
(2) There are a lot of threads waiting for one particular thread to finish.
(3) That thread is waiting to complete a query that *should* complete,
according to everything else in ManifoldCF that I can see. If it
doesn't complete it should detect database deadlock, in any case.
The possibility I am worried about now is that postgresql processes
are dying due to some issue, like memory consumption. We therefore
need to correlate postgresql processes with threads, so if you can get
a ps -elf | grep postgres from the postgres machine and also include
that, it would be great.
Karl
On Mon, Feb 11, 2013 at 11:14 AM, Karl Wright <da...@gmail.com> wrote:
> I've confirmed that there's a deadlock of some kind; it's occurring as
> a result of the hopcount depth tracking. The issue seems to be nested
> transactions; PostgreSQL doesn't appear to be dealing with these
> properly in all cases, and winds up getting a deadlock that it doesn't
> detect.
>
> I have to look carefully at the code to see if it can be restructured.
>
> Karl
>
> On Mon, Feb 11, 2013 at 10:56 AM, Karl Wright <da...@gmail.com> wrote:
>> That is not the reason for the stop. I suspect a deadlock. Trying to
>> verify that now.
>>
>> Karl
>>
>>
>> On Mon, Feb 11, 2013 at 10:44 AM, Erlend Garåsen
>> <e....@usit.uio.no> wrote:
>>> On 11.02.13 16.26, Karl Wright wrote:
>>>>
>>>> trunk has a different schema than 1.1.1. So yes, you'd have to blow
>>>> away the old database to go back.
>>>
>>>
>>> OK, who knows. Maybe this was the reason why it just stopped. I'll clean up
>>> by deleting all tables and related db resources and try again.
>>>
>>> Erlend
>>>
>>>
>>> --
>>> Erlend Garåsen
>>> Center for Information Technology Services
>>> University of Oslo
>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
I've confirmed that there's a deadlock of some kind; it's occurring as
a result of the hopcount depth tracking. The issue seems to be nested
transactions; PostgreSQL doesn't appear to be dealing with these
properly in all cases, and winds up getting a deadlock that it doesn't
detect.
I have to look carefully at the code to see if it can be restructured.
Karl
On Mon, Feb 11, 2013 at 10:56 AM, Karl Wright <da...@gmail.com> wrote:
> That is not the reason for the stop. I suspect a deadlock. Trying to
> verify that now.
>
> Karl
>
>
> On Mon, Feb 11, 2013 at 10:44 AM, Erlend Garåsen
> <e....@usit.uio.no> wrote:
>> On 11.02.13 16.26, Karl Wright wrote:
>>>
>>> trunk has a different schema than 1.1.1. So yes, you'd have to blow
>>> away the old database to go back.
>>
>>
>> OK, who knows. Maybe this was the reason why it just stopped. I'll clean up
>> by deleting all tables and related db resources and try again.
>>
>> Erlend
>>
>>
>> --
>> Erlend Garåsen
>> Center for Information Technology Services
>> University of Oslo
>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
That is not the reason for the stop. I suspect a deadlock. Trying to
verify that now.
Karl
On Mon, Feb 11, 2013 at 10:44 AM, Erlend Garåsen
<e....@usit.uio.no> wrote:
> On 11.02.13 16.26, Karl Wright wrote:
>>
>> trunk has a different schema than 1.1.1. So yes, you'd have to blow
>> away the old database to go back.
>
>
> OK, who knows. Maybe this was the reason why it just stopped. I'll clean up
> by deleting all tables and related db resources and try again.
>
> Erlend
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
On 11.02.13 16.26, Karl Wright wrote:
> trunk has a different schema than 1.1.1. So yes, you'd have to blow
> away the old database to go back.
OK, who knows. Maybe this was the reason why it just stopped. I'll clean
up by deleting all tables and related db resources and try again.
Erlend
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
trunk has a different schema than 1.1.1. So yes, you'd have to blow
away the old database to go back.
Karl
On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
<e....@usit.uio.no> wrote:
>
> The job just stopped working and nothing suspicious in my logs. The database
> people are saying that we have connection locks again ("<idle> in
> transaction").
>
> Karl, you mentioned that in order to use the following parameter:
> <property name="org.apache.manifoldcf.database.connectiontracking"
> value="true"/>
> there was no way back to use an older release due to changes in the
> database. That's ok, but was that just a temporary functionality, which
> means, I need to clear my database in order to use 1.1.1 RC0?
>
> Erlend
>
>
> On 10.02.13 20.01, Karl Wright wrote:
>>
>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>
>> The release artifact can be downloaded from:
>>
>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>
>> There is a tag at:
>>
>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>
>> This release has been made primarily to fix a leak of connection
>> handles, described by CONNECTORS-638. Other major fixes have also
>> been included, specifically:
>>
>> - Fix the maven build (various tickets)
>> - Fix the rather broken Elastic Search connector (also various tickets)
>>
>> Karl
>>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Karl Wright <da...@gmail.com>.
On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen
<e....@usit.uio.no> wrote:
>
> The job just stopped working and nothing suspicious in my logs. The database
> people are saying that we have connection locks again ("<idle> in
> transaction").
>
Then this is a different problem.
Can you get a thread dump of the agents process right now?
Karl
> Karl, you mentioned that in order to use the following parameter:
> <property name="org.apache.manifoldcf.database.connectiontracking"
> value="true"/>
> there was no way back to use an older release due to changes in the
> database. That's ok, but was that just a temporary functionality, which
> means, I need to clear my database in order to use 1.1.1 RC0?
>
> Erlend
>
>
> On 10.02.13 20.01, Karl Wright wrote:
>>
>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>>
>> The release artifact can be downloaded from:
>>
>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>>
>> There is a tag at:
>>
>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>>
>> This release has been made primarily to fix a leak of connection
>> handles, described by CONNECTORS-638. Other major fixes have also
>> been included, specifically:
>>
>> - Fix the maven build (various tickets)
>> - Fix the rather broken Elastic Search connector (also various tickets)
>>
>> Karl
>>
>
>
> --
> Erlend Garåsen
> Center for Information Technology Services
> University of Oslo
> P.O. Box 1086 Blindern, N-0317 OSLO, Norway
> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: [VOTE] Release Apache ManifoldCF 1.1.1, RC0
Posted by Erlend Garåsen <e....@usit.uio.no>.
The job just stopped working and nothing suspicious in my logs. The
database people are saying that we have connection locks again ("<idle>
in transaction").
Karl, you mentioned that in order to use the following parameter:
<property name="org.apache.manifoldcf.database.connectiontracking"
value="true"/>
there was no way back to use an older release due to changes in the
database. That's ok, but was that just a temporary functionality, which
means, I need to clear my database in order to use 1.1.1 RC0?
Erlend
On 10.02.13 20.01, Karl Wright wrote:
> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0.
>
> The release artifact can be downloaded from:
>
> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1
>
> There is a tag at:
>
> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0
>
> This release has been made primarily to fix a leak of connection
> handles, described by CONNECTORS-638. Other major fixes have also
> been included, specifically:
>
> - Fix the maven build (various tickets)
> - Fix the rather broken Elastic Search connector (also various tickets)
>
> Karl
>
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050