>
>
>>
>> Filed a bug. bug# 6463768.
>
>
> Good.
> As an aside: Why aren't we filing this in issue tracker?
In the issue tracker I only saw "9.0pe, 9.0peur1, 9.1pe". I was looking
for a EE category. Now that EE features are exposed in GlassFish, which
is the right version to choose? I will dig up my previous emails to see
if I missed any existing conversations on this topic. I thought all the
bugs are available to view issue tracker soon and 2 way bridge will be
operational soon. I will file the next bug using issue tracker, so that
we do not have wait for 2 way bridge.
>>
>>> [snip] http://docs.sun.com/app/docs/doc/819-2555/6n4r9qo8h?a=view#abdht
>>>
>>> What command would be used to change the
>>> response-timeout/HTTPS-routing/reload-interval/monitor/routecookie
>>> of an established http-lb-config object?
>>>
>> Dotted name command. Hanan, we should document this use case too.
>
>
> The usage of 'asadmin set' is alluded to in this doc,
> http://docs.sun.com/app/docs/doc/819-2555/6n4r9qo8h?a=view. Their
> aren't enough details for the user to be able to use it, without a
> fair bit of digging/GF source level knowledge.
I filed a issue# (using issue tracker) on docs to fix all these issues.
Please add any comments/issues there.
>>
>>> It seems like routecookie is not documented correctly....
>>>
>>> What happens if I use delete-http-lb-config, but do not delete the
>>> loadbalancer.xml file from the machine that has the lb installed?
>>
>>
>> It is not supposed to delete the lb file. delete-http-lb-config only
>> removes the config object on DAS.
>
>
> Is that true even if auto update is enabled?
>
I will back and present hopefully during MS2 timeframe about Auto Update
feature in detail.
> But nothing bad will happen to the users who are accessing apps via an
> LB'ed site that just had its http-lb-config object deleted on the DAS,
> as long as the loadbalancer.xml file still exists, right?
>
Yes.
> I am very worried that the LB and DAS work "together" to make load
> balancing "work"... This worry is triggered by the number of places
> in the docs about the http-lb commands that the order of operations is
> called out... For example: you must create-http-lb-ref, then enable it...
>
> OR
>
> You must disable something before you can delete it...
That is the premise of the design, so that things are transparent. The
caution is placed so that we do not automatically enable things and
delete things which are not empty. User has to explicitly do this or use
an convenience commands to do enabling all instances. The thing missing
is for example delete-http-lb-config --force. where it removes the
config, even things in it. We discussed about it long time back. I
think there was a good reason to not do it. If there is not, I am all
for it. Copying him.
>
>>
>>> [snip]
>>> I have a real problem mapping create-http-lb-ref to content in the
>>> loadbalancer.xml....
>>>
>> Some of our users may also have the same problem of mapping the
>> commands to loadbalancer.xml. I will work with docs to document this
>> more in detail. Copying Hanan from docs.
>
>
> Good.
>
>>
>> [snip]
>>
>>>
>>> Which command allows me to set or change the policy attribute of the
>>> cluster element?
>>
>>
>> Policy support etc is added in 9.0, for example if you look at CLIs
>> in 9.0
>> http://appserver.sfbay/cgi-bin/body.pl?options=/as9ee/navigation.html&content=/as9ee/pm.html&curTab=2,
>> you will get an idea. I will post them on GlassFish soon.
>>
>> create-http-lb-ref [--terse=false] [--echo=false]
>> [--interactive=true] [-
>> -host localhost] [--port 4849] [--secure|-s=true] [--user admin_user]
>> [--passwor
>> dfile file_name] [--lbpolicy policy] [--lbpolicymodule
>> path-to-module] [--health
>> checkerurl url] [--healthcheckerinterval interval-in-seconds]
>> [--healthcheckerti
>> meout timeout-in-seconds] [--lbenableallapplications]
>> [--lbenableallinstances] -
>> -config config_name target
>
>
>
> Is this something that will be presented in more detail at a User
> Experience session?
yes.
>
> (It seems like there are a number of new features of http-lb that did
> not get presented.)
>
Because they are new and not yet completely working. I am happy to come
back and talk about these at a later point.
> Some topics the presentation might want to cover are things like:
>
> What is a policy module? Is there an API that a policy module must
> implement? Is there a DTD or schema that a policy module must conform to?
>
See if you this doc provide enough information. Pankaj can help with any
questions.
http://www.glassfishwiki.org/gfwiki/attach/OnePagersOrFunctionalSpecs/LB-onepager.txt
> What are the semantics of --lbenableallinstances?
>
enableallinstances only valid for enabling during creation. by default
they are disabled. enableallinstances works for only one target, as you
can add one target at a time to lbconfig. there is no create-http-lb-ref
--target c1, c2, c3
create-http-lb-config c1-lb-config
create-http-lb-ref --config c1-lb-config c1
(in memory object)equivalent to the following:
<loadbalancer>
<cluster name="c1">
<instance disable-timeout-in-minutes="30" enabled="false"
listeners="http://
chandu.sfbay:8080
https://chandu:8181 https://chandu:4849" name="server"/>
<web-module context-root="/jaxrpc-simple"
disable-timeout-in-minutes="30" en
abled="false"/>
</cluster>
....
however
create-http-lb-config c1-lb-config
create-http-lb-ref --lbEnableAllInstances --lbEnableAllApplications
--config c1-lb-config c1
<loadbalancer>
<cluster name="c1">
<instance disable-timeout-in-minutes="30" enabled="true"
listeners="http://
chandu.sfbay:8080
https://chandu:8181 https://chandu:4849" name="server"/>
<web-module context-root="/jaxrpc-simple"
disable-timeout-in-minutes="30" en
abled="true"/>
</cluster>
....
>>
>>>
>>> [snip]
>>>
>>> Is the default disable-timeout-in-minutes really 31 or is it
>>> "session idle timeout"+1?
>>
>>
>> Default is 31. disable-timeout-in-minutes CDATA "31"
>
>
> What will happen if the user changes the "session idle timeout" to be
> a value like 60, after they have created their lbxml and used it to
> configure their LB?
This change will appear in lbxml, if they re-export again.
>>
>>>
>>> Is the user required to execute disable-http-lb-server before they
>>> can execute delete-http-lb-ref? The document strongly implies that
>>> the user must do one then the other? Why is that? Why can't we
>>> give the user a SINGLE command to delete the ref? [That command may
>>> perform a disable "under the covers"]
>>>
>>> http://docs.sun.com/app/docs/doc/819-2555/6n4r9qo8h?a=view#abdhv
>>
>>
As of now yes. please see my answers above. will look into this.
>> We prefer do it explicitly on command and not to do "under the covers".
>
>
> Why should we want to force the user to enter two commands instead of
> one???
User has both the choices
1). use one command configure-http-lb-config
2). or multiple commands create-http-lb-config, create-http-lb-ref etc.
>
> I realize there are cases, like rolling upgrades, where the user needs
> to do an explicit disable....
>
yes.
> That implies that we must have a disable command... But it doesn't
> imply that a user must disable, before they delete...
>
I will check with Prashant to see if we can provide this.
>> Unless we hear lot of complaints from users that do it "under the
>> covers".
>>
>>>
>>> Is there a way to enable all the servers in a config with just one
>>> command? Something like:
>>>
>>> asadmin enable-http-lb-servers <config object name>
>>>
>>> or
>>>
>>> asadmin enable-http-lb-server -config <config object name>
>>>
>> Yes, during asadmin create-http-lb-ref --lbenableallinstances
>> --config config_name target and asadmin create-http-lb-ref.
>
>
> I am lost here...
>
> Say I have an http-lb-config (Z) with 3 instances or clusters (a, b,
> c) already created...
>
> How would I use create-http-lb-ref to enable them all at one time? Is
> there an example someplace?
I guess it will be more clear, when documentation for all these new
options is available. Right now there is no 9.0 EE documentation for LB
admin. I have only CLI commands.
Simple answer to question is that no we do not support dealing with
multiple cluster at once at this point. one cluster at a time.
>
>>
>>> It seems like the only way to do this today is to enter an
>>> enable-http-lb-server command for each server or cluster that may be
>>> in the config... That seems like it would be error prone... (people
>>> forgetting to enable an instance or cluster)...
>>>
>>> The same comment would apply to disable.
>>>
>>> http://docs.sun.com/app/docs/doc/819-2555/6n4r9qo8h?a=view#abdhw
>>
Better to make people enable the instances, rather than exposing any
un-intended applications to LB by default. Since we automatically add
applications to LB. The least can do is enable them. Please see my
below comments.
>>>
>>> I have a similar question/suggestion for applications as the one I
>>> just made for servers...
>>>
>>> It looks like enable-http-lb-application implies a
>>> create-http-lb-application operation (adds a web-module entry into
>>> the http-lb-config...). How do I delete a web-module entry from an
>>> http-lb-config? Is there a remove-http-lb-application command that
>>> I missed?
>>
Sorry. I missed these questions.
There is no such thing. User does not have to enlist the applications
in the load balancers. Once user adds a cluster to LB, LB admin code
figures out which applications are deployed on that cluster and adds
those to LB. Similarly once an application un-deployed from a cluster,
it is also removed from those load balancers.
>>>
>>> What command is used to set/change the attributes of a web-module
>>> element?
>>>
This will be clear, once we talk about which element maps which commands
or where that information is obtained from. For example:
<!ELEMENT web-module (idempotent-url-pattern*)>
<!ATTLIST web-module context-root CDATA #REQUIRED -->
comes from domain.xml ( context-root in web-module element for stand
alone modules, for an application it comes from descriptor)
enabled %boolean;
"true" --> asadmin
http-lb-enable-application
disable-timeout-in-minutes CDATA
"31" --> asadmin http-disable-http-application
--timeout (you can only modify during disable, because that is when this
is useful)
error-url CDATA "" >
--> existing bug to fix this
>>> What happens if the user undeploys an app that is enabled for load
>>> balancing?
>>>
>>> http://docs.sun.com/app/docs/doc/819-2555/6n4r9qo8h?a=view#abdhx
>>
>>
>> This is an existing RFE (# 6463784)
>
>
> Which of my previous questions is an RFE?
>
>>
>>>
>>> How do I change the value of the properties that were used/defaulted
>>> when I created a health-checker?
>>>
>> Using the dotted name commands. Hanan, we should include this in the
>> docs.
>
>
> +1
>
>>
>>> It looks like the health-checker has additional properties, like
>>> active-healthcheck-enabled that are set via the property sub-element
>>> of loadbalancer... Why doesn't the health-checker element have a
>>> property sub-element for them?
>>
>>
>> These 2 properties are global to loadbalancer, not specific to a
>> particular health-checker.
>
>
> Which is why they are documented in the section discussing the
> health-checker element?
>
Added to doc-improvement bug.
Thanks again for all the input.
We pushed in the past to do doc campaign to collect use cases and review
from the users/community. It would be nice if our external users review
these and give us comments. That would also dramatically improve our
document and make them very user friendly.
> vbk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>