From dev-return-36554-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Jul 16 11:16:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id CB752180657 for ; Mon, 16 Jul 2018 11:16:03 +0200 (CEST) Received: (qmail 51999 invoked by uid 500); 16 Jul 2018 09:16:02 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 51988 invoked by uid 99); 16 Jul 2018 09:16:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jul 2018 09:16:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 649A41A1D03 for ; Mon, 16 Jul 2018 09:16:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id fSz3M4f0kbWR for ; Mon, 16 Jul 2018 09:16:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4F1745F478 for ; Mon, 16 Jul 2018 09:16:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8D785E0186 for ; Mon, 16 Jul 2018 09:16:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1F21321EE2 for ; Mon, 16 Jul 2018 09:16:00 +0000 (UTC) Date: Mon, 16 Jul 2018 09:16:00 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-9006) Add per-call tracing capabilities for IgniteCache#{get, getAll} methods MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Alexey Goncharuk created IGNITE-9006: ---------------------------------------- Summary: Add per-call tracing capabilities for IgniteCache#{get, getAll} methods Key: IGNITE-9006 URL: https://issues.apache.org/jira/browse/IGNITE-9006 Project: Ignite Issue Type: New Feature Affects Versions: 2.6 Reporter: Alexey Goncharuk Fix For: 2.7 As an experimental feature to debug objects visibility issues, we should add an API method {{IgniteCache#withTrace()}} which will enable per-call API calls tracing. I think we can start with reads tracing, as a simplest change. We need to introduce an additional flag mask to {{NearSingleGetRequest}}, {{NearGetRequest}}, {{Near...Response}} to identify such requests, and when processing, print out all message processing path (send, receive), entry swap/unswap, versions and values read, {{GridCacheEntryRemovedException}}s encountered, etc. For transactional caches, I think it also makes sense to print out all pending transactions that touch the key being read. -- This message was sent by Atlassian JIRA (v7.6.3#76005)