+1 to Dan's suggestion.
In addition we should think about the following scenario:
In certain cases, cleanQueue would cause stop to block if Receivers are not
up or causing exception while applying the events. In that case events will
not be deletd from queue and stop will block.
Currently, it is co
+1 to what Anthony said.
> On Nov 13, 2019, at 8:07 AM, Anthony Baker wrote:
>
> The expectation is that master always points to the latest release (in this
> case 1.10.0). There’s a rel/v1.9.2 tag already—what more is needed? We
> don’t need the release branch since further patches can be
>
> vsd stat in the gfs file
>
Just here to say consider using a meter instead of stat as documented in
https://cwiki.apache.org/confluence/display/GEODE/How+to+add+a+Meter if
more than a log message is warrented.
-michael
On Thu, Nov 14, 2019 at 11:29 AM Nabarun Nag wrote:
> +1 to Dan's sugge
Found an image in the Pivotal Branding folder that had a better-looking TM.
Pushed it to the site - all fixed now.
On Thu, Nov 14, 2019 at 1:28 PM Joey McAllister
wrote:
> Nick: I think the pertinent info on the trademarks page is this:
>
> "The Apache Software Foundation considers the names of
Nick: I think the pertinent info on the trademarks page is this:
"The Apache Software Foundation considers the names of all top level
projects, all downloadable software products, our feather logo, and the
logos of our projects to be trademarks of the ASF. The ASF owns all Apache
trademarks on beh
We have found the vector, which was already modified with the correct TM and a
rendered PNG from it. That should get corrected on the site soon.
> On Nov 14, 2019, at 11:32 AM, Nicholas Vallely wrote:
>
> I feel like maybe this was talked about previously, but does Apache have a
> registered T
I feel like maybe this was talked about previously, but does Apache have a
registered Trademark for Geode? I don't see it on this list:
http://www.apache.org/foundation/marks/list/ which is fine for a TM from
what I know, but could we potentially be stepping on another TM'd thing
called Geode? Is t
+1 to Dan's suggestion
What about a log and a vsd stat in the gfs file which tells us if any
cleanQueue commands were executed.
Regards
Nabarun Nag
On Thu, Nov 14, 2019 at 10:27 AM Udo Kohlmeyer wrote:
> In addition... making is default has bigger consequences that we have
> not thought about
+1
De: Helena Bales
Enviado: jueves, noviembre 14, 2019 7:52 p. m.
Para: dev@geode.apache.org
Asunto: Re: Website Banner Graphic
+1
On Thu, Nov 14, 2019 at 10:47 AM Jacob Barrett wrote:
> Does anyone know who is responsible for our website’s graphics. The
> re
+1
On Thu, Nov 14, 2019 at 10:47 AM Jacob Barrett wrote:
> Does anyone know who is responsible for our website’s graphics. The
> recently added “TM” to the Geode logo needs to be redone. My design brain
> can’t handle that the text is in the wrong font, the wrong color and isn’t
> anti-aliased l
Does anyone know who is responsible for our website’s graphics. The recently
added “TM” to the Geode logo needs to be redone. My design brain can’t handle
that the text is in the wrong font, the wrong color and isn’t anti-aliased like
the rest of the text and graphic components.
https://geode.a
In addition... making is default has bigger consequences that we have
not thought about..
e.g if you purge an existing queue on start up.. is this the start up of
the server node / GS Queue? Given that we have shared-nothing
architecture, purging *should* only be local and not cluster-wide...
+1, I love that idea... Problem is that we don't have sufficient
auditing around managment/Operational tasks.
What happens if this task is run on an active cluster? Without proper
auditing and possibly some notion on WHAT data was purged, this could
open the product up for many head-aches.. i.
+1 to Dan's suggestion
On Thu, Nov 14, 2019 at 9:52 AM Dan Smith wrote:
> I'm ok with adding a --cleanQueue option.
>
> However, I don't think it should default to be true, since that would be
> changing the behavior of the existing command. It should default to false.
>
> -Dan
>
> On Thu, Nov 1
I'm ok with adding a --cleanQueue option.
However, I don't think it should default to be true, since that would be
changing the behavior of the existing command. It should default to false.
-Dan
On Thu, Nov 14, 2019 at 9:28 AM Xiaojian Zhou wrote:
> The --cleanQueue option is a similar idea as
Mario,
Thats the current behavior. When the sender is initially started, it
attempts to connect to the receiver. If it does not connect, it won't retry
until there is a batch of events to send. Look for callers of
GatewaySenderEventRemoteDispatcher.initializeConnection to see the
behavior. It coul
The --cleanQueue option is a similar idea as Barry's "DeadLetter" spike. I
remembered that we decided not to do it.
On Wed, Nov 13, 2019 at 11:41 PM Mario Ivanac wrote:
> Hi,
>
> just to remind you on last question:
>
> what is your opinion on adding additional option in gfsh command "start
>
Owen created a PR to automatically update the geode-native-build image (
https://github.com/apache/geode/pull/4315 ). I think it could be merged in 1.11
release branch too, so the script is used in the next release.
And then I would remove the manual steps from the wiki.
___
18 matches
Mail list logo
