Hi geode dev,
I'm working on upgrade lucene to a newer version. (
https://issues.apache.org/jira/browse/GEODE-7309)
I followed instruction from
https://cwiki.apache.org/confluence/display/GEODE/Upgrading+to+Lucene+7.1.0
Also add some other changes that is needed for lucene 8.2.0.
I found some p
Yes, it passes for me always, too, as I said.
But the background locator JVM logs that scary stack trace about not
finding LogService in the wrong package. Could you please look more closely?
On Fri, Nov 1, 2019 at 4:22 PM Dan Smith wrote:
> Your test passes for me, btw.
>
> -Dan
>
> On Fri, No
And yes, I do ./gradlew clean daily despite previously being told not to on
this list.
I will make sure that dunit suspect string grep is working on the
background locator JVM in dunit. If it's not (which I suspect) then it'll
start failing on that stack when I fix suspect-grep.
On Fri, Nov 1, 20
If it is picking up an old version of geode then it's doing so because we
use old versions for upgrade/backwards testing. The only old versions of
the jars I have are the ones that our build pulls down for the upgrade
tests. These old versions do tend confuse intellij so it's possible it's a
proble
Kirk, will you craft a Jira about this for the "Build" component, and
assign it to me?
On Mon, Nov 4, 2019, 09:30 Kirk Lund wrote:
> If it is picking up an old version of geode then it's doing so because we
> use old versions for upgrade/backwards testing. The only old versions of
> the jars I h
Build Update for apache/geode-examples
-
Build: #387
Status: Errored
Duration: 1 min and 34 secs
Commit: 5a57cfb (release/1.11.0)
Author: Mark Hanson
Message: Prepping for 1.11.0 release
View the changeset: https://github.com/apache/geode-examples/commit/5a57c
I filed https://issues.apache.org/jira/browse/GEODE-7403 and I'm currently
trying to:
a) determine if it reproduces in both CLI and IntelliJ (IntelliJ so far
with a clean checkout of develop)
b) determine why an error-level log message logged by the background dunit
locator is not causing a LogCon
Kirk and I tracked this down. He had a GEODE_HOME environment variable
which the locator was picking up and finding an old war file from.
-Dan
On Fri, Nov 1, 2019 at 4:16 PM Dan Smith wrote:
> Hi Kirk,
>
> Did you do a ./gradlew clean? It looks like you might be picking up an old
> version of o
Build Update for apache/geode-native
-
Build: #2176
Status: Passed
Duration: 1 hr, 37 mins, and 17 secs
Commit: 24c5c78 (release/1.11.0)
Author: M. Oleske
Message: Resolve LGTM issues in ThinClientPoolDM (#543)
* LGTM issues in ThinClientPoolDM, among other th
Looks like the Management service blows up
with ClassNotFoundException:
org.apache.geode.logging.internal.log4j.api.LogService
This seems related to the previous ClassNotFoundException, except that in
this instance, the LogService which cannot be found is in the correct
package. Please disregard t
1) nevermind
2) any time you change branches, do yourself a favor and always do a clean
build:
$ ./gradlew clean
$ ./gradlew build installDist -x test
For anyone who's wondering... yes I keep GEODE_HOME configured in my run
configuration in IntelliJ because I've been following ATDD in my daily wo
Hello Geode Dev Community,
We have created a new release branch for Apache Geode 1.1100 - “release/1.11.0"
Please do review and raise any concern with the release branch.
If no concerns are raised, we will start with the voting for the release
candidate soon.
Regards
Mark Hanson
Argh... Corrected release version below…
> On Nov 4, 2019, at 4:47 PM, Mark Hanson wrote:
>
> Hello Geode Dev Community,
>
> We have created a new release branch for Apache Geode 1.11.0 -
> “release/1.11.0"
>
> Please do review and raise any concern with the release branch.
> If no concerns a
I think the issue probably has to do with doing a rolling upgrade from an
old version of geode (with an old version of lucene) to the new version of
geode.
Geode's lucene integration works by writing the lucene index to a colocated
region. So lucene index data that was generated on one server can
Hi geode dev,
we have some questions regarding gateway senders and gateway sender queue.
* During testing we have observed, different behavior in parallel and
serial gateway senders. In case we manually stop, than start gateway senders,
for parallel gateway senders, queue is purged, but for
15 matches
Mail list logo
