Skip to content

Doc 4308 #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 29, 2018
Merged

Doc 4308 #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
75418fe
Eventing - Fix issue re timers in the v5.5 docs set (#3)
amarantha-k Sep 11, 2018
b359baf
resolving merge conflicts
maheshnagarajCbase Oct 16, 2018
2b433fa
DOC:3816: Changes to the doc as suggested in the bug along with local…
maheshnagarajCbase Oct 16, 2018
c036bed
DOC-4308:Changes as suggested in the bug
maheshnagarajCbase Oct 25, 2018
4b9ef36
Merge branch 'release/6.0' into DOC-4308
maheshnagarajCbase Oct 29, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/eventing/pages/eventing-Terminologies.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,3 +119,4 @@ Newly created handlers start in an undeployed state.

When a Function gets deleted, the source code implementing the Function, all processing checkpoints, and other artifacts in the metadata provider are purged.
Before deleting, make sure you have undeployed the Function.

3 changes: 3 additions & 0 deletions modules/eventing/pages/eventing-debugging-and-diagnosability.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,9 @@ NOTE: The *cbcollect_info* tool does not collect the Application log files.
| /Users/<user>/Library/Application Support/Couchbase/var/lib/couchbase/data/@eventing
|===


NOTE: During Cluster setup, if you have chosen a custom path, then the path for Application logs is same as that of the selected Indexes Path. The @eventing folder in the selected Indexes Path stores the Application logs.

To configure an Application log, use the REST endpoint settings option.

*Sample URL*: `192.168.1.5:8091/_p/event/api/v1/functions/<Function_name>/settings`
Expand Down
2 changes: 2 additions & 0 deletions modules/eventing/pages/eventing-faq.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,7 @@ These are the meta fields associated with the document. For more information, re

* What is the metadata bucket? Do I need to create a separate bucket?
+

To provide better restartability semantics when an Eventing node is offline, some metadata needs to be stored: a Couchbase bucket solves this problem.
Setting up the metadata bucket is a one-time activity that is done cluster-wide.
It is recommended that the metadata bucket not be used for any other data-storage (which is to say, it should not be accessed by any other application).
Expand Down Expand Up @@ -178,3 +179,4 @@ When the Eventing node experiences a failover condition, few mutations may be pr
* Does a rebalance have any effect on the firing of events?
+
No. Functions do not lose any mutations during a rebalance operation.

1 change: 1 addition & 0 deletions modules/eventing/pages/troubleshooting-best-practices.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,3 +76,4 @@ Ensure that you configure the script timeout value after carefully evaluating th

As a best practice use a combination of try-catch block and the application log options.
This way you can monitor, debug and troubleshoot errors during the Function execution.